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
Duplicate strings - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Sun Feb 11th, 2018 10:43 am
PM Private Upload Quote Reply
josefder1
Member
 

Joined: Mon Aug 6th, 2007
Location: Offingen, Germany
Posts: 91
Status: 
Offline
Hello,

If I use "Duplicate strings" translation with "By Original and Context" and the Original and Context are in different files the translation didn't work because I think the comparison process checks as context also the filename.

E.  g.

I have the same context but in different files the duplicate translation didn't work.

These are the contexts

E:\Bricscad\uerbsetz\sources\Bricscad (Linux)\V18\Resources\options.xml.CmdOptions.menu.toolpanel.name.Instruction

E:\Bricscad\uerbsetz\sources\Bricscad (Windows)\V18\Resources\options.xml.CmdOptions.menu.toolpanel.name.Instruction


Is it possible to exclude the filename while comparing the context?

Regards
Walter

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 13th, 2018 10:04 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

to my knowledge the switch "Use smart method" is related to partitial context. Since it is mussing in the manual I asked R&D for some background info.

Markus




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

 Posted: Thu Feb 15th, 2018 04:29 am
PM Private Upload Quote Reply
josefder1
Member
 

Joined: Mon Aug 6th, 2007
Location: Offingen, Germany
Posts: 91
Status: 
Offline
Hi Markus,
I have tested this with "Use smart method", but it makes no difference whether the switch is on or off

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 15th, 2018 07:26 am
PM Private Upload Quote Reply
Emiliano
Member
 

Joined: Sun Nov 14th, 2010
Location:  
Posts: 65
Status: 
Offline
I have the same problem too.
It is extremely difficult to trust the duplicate translation of Sisulizer when the project contains several different files.

The BricsCAD options.xml file must respect a very precise syntax and a wrong translation can prevent the correct functioning of the software!

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 15th, 2018 08:49 am
PM Private Upload Quote Reply
MPalaoro
Member
 

Joined: Thu Feb 15th, 2018
Location: Brazil
Posts: 2
Status: 
Offline
josefder1 wrote:
...
Is it possible to exclude the filename while comparing the context?

Regards
Walter

Hello,

I'd like to support Walter. I have the same issue for Portuguese language versions on BricsCAD.

Thanks,
Miguel

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 15th, 2018 10:25 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

I understand that in some situations it can become handy and asked R&D about that.

In other situations - where the context name in different modules is the same while the content is totally different - this can make major problems. It must be clear to users that the context in such mode is not unique. Something our R&D has to consider. Setting the switch wrong could help to overwrite existing translations. Its like unlocking the door of a washing machine in process. If you are sure the water level is not to high and you know what you do it is no problem. But for others the protection has a good reason.

I hope our R&D has some clever idea to this :-)

Markus



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

 Posted: Thu Feb 15th, 2018 10:44 am
PM Private Upload Quote Reply
MPalaoro
Member
 

Joined: Thu Feb 15th, 2018
Location: Brazil
Posts: 2
Status: 
Offline
Markus.Kreisel wrote:
...
It must be clear to users that the context in such mode is not unique...
Markus

Hi Markus,

In our case, for BricsCAD, the different contexts are related with Operational Systems versions, and the intrinsic meaning of each context is accurately the SAME for each version.

The option could be made available for each user, on Options:
"The context are the same on each version:" Yes/No.

A simple option would prevent mistakes for diverse situations.

Thanks,
Miguel

Back To Top PM Private Upload Quote Reply

 Posted: Fri Feb 16th, 2018 05:26 am
PM Private Upload Quote Reply
josefder1
Member
 

Joined: Mon Aug 6th, 2007
Location: Offingen, Germany
Posts: 91
Status: 
Offline
Hi Markus,
in our case, it's the other way around. If we translate duplicate strings only after the original will have very many incorrect translations. If we could translate according to the original and context, these errors would be avoided or at least reduced.

I also see the problems with incorrect usage, but this is actually the translator's problem.

Or there may be a possibility to define the setting for duplicate strings directly at the source properties and not globally for a project.

TX
Walter

Back To Top PM Private Upload Quote Reply

Current time is 11:47 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Duplicate strings



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