globalization of xslt

Question

1.00/5 (1 vote)

See more:

Hi All,

I have 100+ xslt files which i used as templates. If i need to display the xslt in different language say Spanish how can i achieve that? I have one xml file from which 100+ xslt files are created to display the contents... Do i need to create resource files for each xslt? Is there any other approach?

Thanks.

Posted 10-Jun-13 8:21am

vidkaat

Add a Solution

Comments

Sergey Alexandrovich Kryukov 10-Jun-13 14:27pm

Display XSLT itself or XML processed (transformed) with XSLT?
—SA

vidkaat 10-Jun-13 15:15pm

When you display xslt itself you mean to say convert xslt file in english to another xslt file in spanish?I am not sure what u r asking?

Sergey Alexandrovich Kryukov 10-Jun-13 15:46pm

No, I mean XSLT is used to transform some XML file to something, so three files are involved. What should be globalized?
—SA

vidkaat 10-Jun-13 16:06pm

Sir,
Can the xml be globalized? I am very new to Globalization....I want the end result to be in Spanish. Globalizing the xslt file is painful i think because there are 100+ xsl files. I would like to know your suggestion on this. Thanks for ur time?

Sergey Alexandrovich Kryukov 10-Jun-13 16:16pm

Not the XML itself. I don't think there is a dedicated mechanism just for XML. It can be globalized in wider context, as a part of some globalized application.
And creation of many localized files is still unavoidable. There is no such thing as miracle. Automatic translation? hardly, best modern translator does not cope with such tasks, at best, they could only be used to assist a qualified human translator.

See also:
http://www.gala-global.org/localization-term/xslt-0
(But it won't provide a solution.)

(By the way, you did not answer my question, but I can guess what's involved...)
—SA

vidkaat 10-Jun-13 16:20pm

Yes the xml is a part of the globalized application. So in this case the xml will also be globalized is it?

Sergey Alexandrovich Kryukov 10-Jun-13 16:30pm

You are still not answering my question: which XML? XSLT or the one which should be transformed. This is important. If XSLT is the part of the project, and XML to be transformed is supplied by the user, this could be a problem, because, how can you enforce that the culture required by the user from your project matches the culture of the XML he supplies? (In principle, it could be ignored.)
Or, those XMLs are also predefined in the project. In both cases, you should use project globalization.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2013-06-10T10:38:00

Please see my comments to the questions. It depends on your scenario; and you did not yet answer to my questions about it.

However, in all cases, if your XMLs (XSLT or other) should be globalized, it means that you need to put all "fixed" XML in the project resources; and your runtime would need to use those resource. You cannot avoid writing XMLs in different versions for different cultures. For each localization, you will need to write resource-only assemblies separately and put all localized XMLs there. Such assemblies would work as satellite assemblies and would be selected automatically when your application thread(s) change culture.

You can read about this mechanism here:
http://msdn.microsoft.com/en-us/library/aa292205%28v=vs.71%29.aspx[^],
http://msdn.microsoft.com/en-us/library/sb6a8618%28v=vs.110%29.aspx[^],
http://msdn.microsoft.com/en-us/library/21a15yht.aspx[^].

—SA