Chinese Simpl and Trad - Build/output file overlaps - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Support forum of the software localization tool Sisulizer

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Chinese Simpl and Trad - Build/output file overlaps

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

Page: 1 2

Printer Friendly

Chinese Simpl and Trad - Build/output file overlaps - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Author

Post

Posted: Thu Aug 14th, 2008 12:07 pm

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

My project consists of English original translated into 13 languages, amongst them Chinese Simplified and Traditional. The mentioned languages are chosen from the default system language list of Sisulizer. No sub-languages chosen.

When choosing Project|Build item, or Build all, the added file extension for both Chinese languages is zh. The later build (e.g. Traditional) overwrites the previous (e.g. Simplified) so that the final result is only one file containing Chinese translation.

Build report details;

Report generated by Sisulizer (version 2.0.269) on 14.08.2008 at 12:56:49
Building "D:LocalizationStringsBuildszhnoc_eng.ts", the Chinese, Simplified version of "D:LocalizationStringsSourcenoc_eng.ts"

Report generated by Sisulizer (version 2.0.269) on 14.08.2008 at 13:02:48
Building "D:LocalizationStringsBuildszh.tranoc_eng.ts", the Chinese, Traditional version of "D:LocalizationStringsSourcenoc_eng.ts"

The reports look similar except part of path changes from zh.tra to zh. From this I would expect two folders named zh and zh.tra to be added under the Builds folder. Or - as the build process does not make folders for other languages either - that the file extension would differ. However, both Chinese languages uses zh as file extension when building translated files. Why is this?

I would like to use the three letter ISO-language code abbreviation. Can I change to this somewhere in the software?

Can I define the output filename my self?

Last edited on Thu Aug 14th, 2008 12:09 pm by Eva

Posted: Thu Aug 14th, 2008 12:23 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

I will test this issue with VCL project with included both Simplified and Traditional Chinese language.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 14th, 2008 01:30 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

I tested my VCL project with following file template: <sl>\<body>.<sl>, and latest version of Sisulizer (269) correctly builds both Traditional (zh.tra) and Simplified (zh) output language files for project. You can change template name of targeted file in source properties dialog window (source context menu > Source Properties or menu Project > Edit Source, tab File). Look on screenshot.

Attachment: screen.png (Downloaded 60 times)

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 14th, 2008 01:33 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Below is short information about available parameters for name template:

<sl> Sisulizer's locale is used. For example "en" is for English, "en-US" is fo English (United States), and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese is "zh.tra".

<iso> ISO locale code is used. It is combination of language and country. For example "en" is for English, "en_US" is fo English (United States), and "zh_TW" is for Traditional Chinese. ISO language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.

<net> NET culture code is used. It is combination of language and country. For example "en" is for English, "en-US" is fo English (United States), and "zh-TW" is for Traditional Chinese. .NET language code does not have any way to code a country.

<win> Windows locale code is used. It contains two or three upper case characters.
For example "EN" is for English, "ENU" is for English (United Stated), and "CHT" is for Traditional Chinese.

<mfc> MFC locale code is used. It contains three upper case characters.
For example "ENE" is for English, "ENG" is for English (United Kingdom), and "CHT" is for Traditional Chinese.

<nls> Windows locale id is used. It is a integer number containing the primary and sub language ids.

<hex> As above but four digit hex value is used instead decimal value.

If you want to get more information, please click on Help button on File tab of Source properties or visit this site: http://www.sisulizer.com/online-help/DelphiSourceDialogFileSheet.htm.

Best regards,

Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 14th, 2008 02:51 pm

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

Thank you for your quick reply!

I know of the properties menu you mention and thank you for leading me to the correct help page to this issue, showing all available parameters.

However, I am not able to open the attached image. If it contains a screenshot showing where to add and how to script the file and language parameters, then I really need to see it. I am not so familiar with scripting parameters...

Could you be so kind as to email it to me?

Posted: Thu Aug 14th, 2008 03:13 pm

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	832
Status:	Offline

Hi Eva,

the screenshots are only shown if you visit the forum and not in the info mail you got. If you follow this link http://forum.sisulizer.com/forum4/962.html you should be able to see all images.

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 14th, 2008 03:26 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

If you want to see images you should to login to forum, because images are invisible for not logged users (they see only names of images).

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Aug 18th, 2008 08:39 am

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

Janusz, thank you for emailing me and for not giving up on me. For some reason the image did not show the first time I logged in to this web-forum last Thursday. However, today it displays fine.

And now I understand why I was confused about where to put the scripting for output purposes. Attached you will find a screenshot of the dialog that shows when I choose Properties|File from module/source in my Sisulizer project. Practically no available choises to make. Maybe it differs a lot due to the source file-type. Yours being Delphi, mine being Qt source...?

Attachment: QtSource_dialog.bmp (Downloaded 48 times)

Posted: Mon Aug 18th, 2008 09:35 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

I have used VCL example, because it is one of most popular platforms. For every platform Sisulzer use a bit different source properties dialogs, appropriated to selected platform environment and source file properties. Unfortunately, I haven't QT translations in my database. Could you send your SLP and source file on support (at) sisulizer.fi?
It allows me better analyze your issue.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Aug 18th, 2008 01:56 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Thank you for files. You are right, both Traditional and Simplified files have this same extension _zh.ts and it could be a bug in our software, and for this reason I will forward this issue to our R&D. Issue is concerned only to file pathnames, because contents targeted language files builds by Sisulizer is different, and for this reason I can offer you temporarily solution for build Traditional and Simplified language files, and you can use it to the moment of release version with fixed pathnames issue:
1. Go to menu View > Edit language > Chinese, Simplified
2. Go to menu Project > Build item (instead Build All)
3. Go to folders with targeted language files and change part file name from _zh.ts to _other name
4. Go to menu Project > Build All
5. Change all file names _zh.ts to _zh.tra.ts
6. Revert all filenames for Simplified to _zh.ts
Because you have many Traditional and Simplified language files in many folders I suggest you create some simple batch file for rename all these files at once instead manually changing.
Excuse me this complicated solution, but it is work, and as I mentioned above it is only temporarily solution. Of course, we will inform you investigation results.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Aug 18th, 2008 02:50 pm

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

Thank you so much for dealing with this.

I have already made a few batch-files to solve the issue meantime. Not so different from what you suggest. But thank you anyway

.

I will be looking forward to receiving the fix when time comes.

Posted: Wed Aug 20th, 2008 06:43 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

I improved Qt localization:

1) Implemented support for wild cards file name (e.g. *.ts) so you do not have to add each files but only one wild card.

2) Implemented feature where you can give out file pattern. By default this <file>_<iso>.<ext> that makes Sisulizer to add _two-letter-iso-code between extension and base file name

sample.ts
->
sample_fi.ts (Finnish)

3) Implemente safe Chinese extension that adds country part to Chinese file name. So when localized to Simplified zh_CH is added insted of zh and zh_TW for Trad.

I would like to use the three letter ISO-language code abbreviation. Can I change to this somewhere in the software?

Currently Sisulizer does not support three letter ISO codes but you can use MFC codes. They are like three letter ISO code but upper cased. See screenshot.

All above will be in build 270 that will come next week.

Jaakko

Attachment: Untitled.png (Downloaded 29 times)

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 21st, 2008 10:26 am

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

This all looks very nice. Perfect.

I have one question though. Regarding 2). My source file is called eng.ts (where eng means English) and I want the output to be named e.g. dan.ts for Danish output, deu.ts for German output, and so on.

Does the fix you refer to mean that I can chose to name the translated output file with language abbreviation only, like this;

Source file: sample.ts
Output file: FIN.ts

by exchanging the <iso> parameter with <MCF> parameter? Or does the original source file name always have to be included?

Posted: Thu Aug 21st, 2008 11:00 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

Yes. If you do not write <base> or <file> to the pattern but just

<mfc>.<ext>

Sisulizer will create file that contains only language part and extension.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 21st, 2008 11:35 am

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

I see. Thank you for explaining this. It seems we need to follow the Qt naming convention in our systems to adjust.

Posted: Thu Aug 21st, 2008 12:28 pm

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

When I implemented comment scanning and tested your files if found one issues.

<context>
<name>clients</name>
<message>
    <source>Clients</source>
    <comment>pageheader</comment>
    <translation>Clients</translation>
</message>
...
<message>
    <source>Clients</source>
    <comment>clients_label</comment>
    <translation>Clients</translation>
</message>
...
</context>

You have the same string (Clients) twice. TS files do not contains any messagecontext tag so Sisulizer uses uses source tag as comment. This means Sisulizer scan the above to message blocks as one item and not separate items as you might think.

A solution would be a context tag. For example

<context>
<name>clients</name>
<message>
    <context>Clients1</context>
    <source>Clients</source>
    <comment>pageheader</comment>
    <translation>Clients</translation>
</message>
...
<message>
    <context>Clients2</context>
    <source>Clients</source>
    <comment>clients_label</comment>
    <translation>Clients</translation>
</message>
...
</context>

But I don't know if you can do this because Trolltech tools do not support it. I need to contact them but it might take some until I get an answer. Do you have any idea how to make difference between these duplicate items.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 21st, 2008 12:41 pm

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

I checked from Qt's documentation about tr fucntion. It seems that you can only pass original string and comment string. So it is impossible to add any other information.

This is a bit odd. Qt allows you call tr() twice with some original string (this is OK) but it adds a separate items for each call.

I will fix this such way that if there are duplicate items Sisulizer will add #n in the end of the string (n is the index of the item). This fix will be in the next build.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 21st, 2008 01:10 pm

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

I fixed this. Next build can handle duplicate items as separate items.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Aug 21st, 2008 02:19 pm

Eva
Member

Joined:	Thu Aug 14th, 2008
Location:	Norway
Posts:	13
Status:	Offline

First of all, I think you have continued posting discussion on a different issue :O)

Secondly, I have discussed this <comment> issue with internal staff as I do not know Qt my self. It has been difficult to get an answer a the time being, however, I have learned that the <comment> tag acknowledged as unique identificator to our systems. That is why we can differ between Clients, Clients and Clients in source text. The source tag is not the unique identificator, the comment tag is.

If using <comment> tag as ID is a Qt convention, would it be possible to get Sisulizer to include this tag as differentiator?

Posted: Thu Aug 21st, 2008 02:34 pm

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

You are right. I mixed two posts

I found a solution for duplicate items. Sisulizer will add an index part to the context of duplicate items. The fix will be in the next build.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Current time is 04:53 pm	Page: 1 2
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Chinese Simpl and Trad - Build/output file overlaps

WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize