|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Your thoughts on custom terminology
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Your thoughts on custom terminology - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Frede Member
|
We have customers that work in different industries, e.g. manufacturing, healthcare and the financial sector. They need custom terminology for some terms that exist in our software. The term "product" could be called "service" when the product is used in the financial sector for example. We would like to create a standard set of terminology for different industries so whenever our software is installed at a customer in the financial sector, we would also install the accompanying resource files for the financial sector. I have done this already for our Swedish translation by creating a variant. Then I only need to change the custom terms in the variant and it will use the standard Swedish translation for all other translations. I was thinking of doing the same thing with the terms for the different industries. However, there is a good chance that some customers that are for example in the financial sector would require some specific terminology that is unique for just them and that could not be added to the general terms for the financial sector. My question is how I would go about in creating that. Is it possible to have a variant of a variant or how could I do that? I hope you understand my question Frede
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, You could create special language variants for them. Instead of German (Germany) you use German (CustomerName). For the distribution you just have to rename the file extension from your custom made extension to .de. That should do the trick. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
Yes, that's what I've done today with one customer but I want to be able to do the following Original (English) |___German standard translation |__ German with adjusted terms for financial sector |__ Client-specific terms for a single client The client-specific terms are for a German company within hte financial sector who needs some custom terminology The client-specific versions is a.. modified version of German with adjusted terms for the financial sector which is.. a modified version of standard german which is.. a translation from English. From standard German to financial-specific, only some terms will be changed. From financial-specific to client- specific, only some terms will be altered. What I guess is needed in this case is to be able to base one variant on another variant, is that possible? Last edited on Thu Sep 10th, 2009 06:31 pm by Frede |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Since you can only have one original language in one project this seems to be impossible. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:24 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Your thoughts on custom terminology | |
Sisulizer software localization tool - Three simple steps to localize