mirheesc
-
all messages by user
20.06.2013 01:06:32
Topic:
Encoding
Scott Rhee
|
Support wrote:
Make the same change for the stylesheet in the Version 9 installation.
With the next RC-WinTrans 9 update (builds after 9.1.0.98 (Feb. 2011)) the "MLParser-WixLocalization.xsl" will have utf-8 output.
.
edited by Support on 06.05.2011
I'm using 9.2.0.5 but the problem still persists. I can manually edit the file though. |
20.06.2013 01:12:34
Topic:
Encoding
Scott Rhee
|
lakuda wrote:
Hello! The question of utf-8 output is resolved. But there appeared one more thing - how is it possible to make target files with different codepages depending on the language used? Now if I write wxl targets, codepage is always 1252 for any language in them.
I don't know how to "intelligently" set the code page as per culture, but at least it's possible to avoid overwriting on that code page and set it differently on RC-WinTrans UI.
This is a part of my XMLParser-WixLocalization.xsl:
<!-- **************************************************************************************************** -->
<!-- 'Culture' attribute (make a TU for the attribute and a Group for th "WixLocalization" element) -->
<xsl:template match="wx:WixLocalization">
<xsl:element name="{local-name(.)}">
<xsl:attribute name="rwt:group" >WixLocalization</xsl:attribute>
<xsl:attribute name="rwt:attributeTU_Culture" >Culture</xsl:attribute>
<xsl:attribute name="rwt:attributeTU_Codepage" >Codepage</xsl:attribute>
<xsl:apply-templates
select="*|@*|text()|comment()|processing-instruction()"/>
</xsl:element>
</xsl:template>
<!-- **************************************************************************************************** -->
Here, I appended a new line of 'rwt:attributeTU_Codepage'. I am not familiar with the syntax of this file but it seems to work - now I can set code pages per each culture on RC-WinTrans UI just like 'Culture' field. |
|
1
|
Powered by AspNetForum 6.9.6.0
© 2006-2010 Jitbit Software