 |
|
|
Hi,
Is there a way to temporarily enable an XSLT2 character-map. My
use-case is generating
python code which will contain string literals. Some of the code I'm
generating looks like
this...
Check_Range_IADAS001_0 = make_range_check("Check_Range_IADAS001_0",
"IADAS001", "IGQS572", GT, "10", "Max = 10")
This particular line is fine but the string "Max = 10" is coming
directly from the input document
and it might contain things which need to be escaped in a python
literal (e.g. ", ' etc). I thought
I could use character-maps but my understanding is that you have to
apply one to an entire final
result tree so if I were to have....
<xsl:character-map name="python-map">
<xsl:output-character character=""" string="\""/>
</xsl:character-map>
It would escape all instances of """ in the output which is not what I want.
Am I trying to use the wrong tool here?
Many Thanks,
Andy
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
