home recent topics recent posts search faq  

Schaudin.com Forum



register | lost password | |
Messages in this topic - RSS

Home » Feature Requests and Suggestions » Encoding

Submit suggestions for expanding/improving RC-WinTrans products.
25.04.2011 09:35:09

lakuda
lakuda
Posts: 28
I'm still using RC-WinTrans 8, going to upgrade it to the 9th version. And I'm testing the 9th demo-version. In both versions I come across one and the same problem - working with wxl-files and generating target wxl's, for example, in Korean, I can't change encoding and that's why all targets are written with "???" signs instead of Korean. Is there already any solution to this problem? Or maybe I'm missing something..
0 permalink
26.04.2011 00:00:15

Support
Support
Administrator
Posts: 210
Hello lakuda,

1. go to the following RC-WinTrans (X8) installation folder:
.\RC-WinTrans X8\FileConverters\

2. use a text editor and open the XML parser stylesheet file
"MLParser-WixLocalization.xsl"

3. change the output encoding
. . . from: < xsl:output encoding="Windows-1252" />
. . . to: < xsl:output encoding="utf-8" />

Then the translated target XML files will be "utf-8" encoded.
0 permalink
27.04.2011 09:17:13

lakuda
lakuda
Posts: 28
Thanks! And what should be done in the 9th version? This file is only readable in it.
0 permalink
28.04.2011 21:04:46

Support
Support
Administrator
Posts: 210
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
0 permalink
26.06.2011 08:33:41

lakuda
lakuda
Posts: 28
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.
0 permalink
27.06.2011 23:10:27

Support
Support
Administrator
Posts: 210
You could use an XSL transformation to convert/copy a translated UTF-8 XML file (created by RC-WinTrans) to any encoding supported by an XSL processor (e.g. by the msxsl.exe command line tool).

Sample files: download "ConvertCodePageXMLFile.zip"
Command line: msxsl.exe UTF8-Input.xml TransformCodePage.xsl -o Win1252Output.xml
Description: transforms/copies an UTF-8 xml file ("UTF8-Input.xml") to a "Windows-1252" encoded xml file ("Win1252Output.xml").
See also at opentag.com ...
0 permalink
20.06.2013 01:06:32

Scott Rhee
Scott Rhee
Posts: 2
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.
0 permalink
20.06.2013 01:12:34

Scott Rhee
Scott Rhee
Posts: 2
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.
0 permalink
24.06.2013 21:31:20

Support
Support
Administrator
Posts: 210
Hello Scott,

adding this line with the attribute "rwt:attributeTU_Codepage" is what needs to be done to make the 'Codepage' attribute localizable.

We have also added this to our "XMLParser-WixLocalization.xsl" stylesheet. In addition the third WixLocalization attribute "Language" can now be localized as well.
The updated stylesheet will be available in RC-WinTrans 9.3 to be released at the end of June 2013.

Regards,
Support, Schaudin.com
.
edited by Support on 02.07.2013
+1 permalink




Powered by AspNetForum 6.9.6.0 © 2006-2010 Jitbit Software