Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support 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.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Can't find a specific literal in Sisulizer project - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Thu Mar 21st, 2019 11:19 am
PM Private Upload Quote Reply
Techedge
Member
 

Joined: Thu Mar 21st, 2019
Location:  
Posts: 2
Status: 
Offline
Hi,

We're recent users of Sisulizer Professional and we're having a hard time localizing a specific literal.
We're working with two translation projects:
1. Spanish PTV_ES.rc created by our developers that we translate into English PTV_EN.rc.
2. We then use the translated PTV_EN.rc as source for many other PTVs in more than 20 wolrdwide languages.

One of those literals is a simple "L" (Monday's initial in Spanish "Lunes"), referenced internally as IDS_SK_0072 as you can see in the the top left picture in the attached combo.jpg.

For some reason that we can't understand, this literal doesn't appear in the Sisulizer project, despite being exactly equal in terms of reference name and length to many other literals you can see in the same screenshot.

As you can see in the bottom screenshot, all other literals of the sort are displayed without problem, while there are other instances of "L" literal that are also displayed OK. The only discriminating factor between those and the missing one is that the latter is a string, and the others are menu items.

Finally, we must specify that to make sure we're not missing anything, we've enabled all source types without any filtering as you can see in the top right screenshots.

Any help would be greatly appreciated here.
Thanks a lot in advance.

BR,
Seb

Attachment: ComboSisu.png (Downloaded 7 times)

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 21st, 2019 01:24 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3222
Status: 
Offline
Hi,

First: it`s very uncommon to localize the source files (.rc) instead of the resources in the binaries. You have a much easier life if you use the recommended path which is tested in uncountable projects.

Anyway...

It looks like the parser has a problem to detect "L" as a string an not as the suffix L (for UNICODE). Can you please change this line to

... L"L"

Or

... "L\0"

to see if the problem goes away. If it is so we know the reason and you have a workaround for now.

https://docs.microsoft.com/en-us/windows/desktop/menurc/rcdata-resource

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 21st, 2019 04:13 pm
PM Private Upload Quote Reply
Techedge
Member
 

Joined: Thu Mar 21st, 2019
Location:  
Posts: 2
Status: 
Offline
Hi Markus,

Thanks for the reply. No clue what you mean buy localizing in the binaries though, we produce .dll from the .rc itself.
I did a test and inserted manually in the PTV_EN.rc the string "M" instead of "L" and open the project English-Many with it and this worked without a prob: IDS_SK_0072 was correctly displayed.
So for the time being I'll create a batch that triggers this edit into the PTV_EN.rc after it's being written in our Spanish-English project, but if you could fix this behavior down the road, that'll be appreciated.
Thanks a bunch in advance.

BR,
Seb

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 21st, 2019 08:10 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3222
Status: 
Offline
I think 99.9 of 100 customers localize their binaries. If you create a new project your choose your .EXE and Sisulizer finds all dependencies and compiled resources. If you use "Build" Sisulizer creates localizes binaries ready to ship to your customers. Depending on the platform even with language runtime change.
But I see in your profile you do not use one of the major platforms like .NET, Delphi, C/C++, Java, ...
Good you found some work around based on the info. I give that error report to R&D. I just can't promise when it will be fixed.
Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 10:36 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Can't find a specific literal in Sisulizer project



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize