Small Tool Help in Translating NopCommerce

while translation is not an easy task in nopcommerce

I searched alot for a tool to help me translating NopCommerce and found this simple tool (http://madskristensen.net/post/A-NET-resource-editor-application-for-resx-files.aspx) created by  Mads Kristensen.

but it works only with resx files [indevidual files], So I do some modifications on it to read XML files and do some classifications for project sections to make it easy to translate.

you can download this small tool from here  http://www.2Daytech.com/NopCommerceTranslator.zip  and give it a try ...

Screenshoot
http://www.2daytech.com/nopcommercetranslator.png

How to use

   1-Download latest english package [The xml file].
   2- Open the exe file and browse to the location of xml file.
   3- Strat to translate.
   4- Upload in your language.

Important Note : backup your XML file before use.

We give it a shot...

We find it easier to compare previous version of rsourcestring and only change the added changes. But if you need to translate from ground up then this tool is handy.

this can be done in the resources page in administrator ,

we can create a button to generate all new added resources by looping on all resources and match with your language then list all new resources...

All I get is a error message saying the it is in the wrong format and that the URL can't be empty... What's wrong?

All I get is an error message saying the it is in the wrong format and that the URL can't be empty... What's wrong?

funkan wrote:

tell me the steps to get this error ... ?

When I try to open the file. If I use the attached XML-file (the English one that comes with the download) and change the text for the text in the XML I want to use, the same error occurs.

I found the problem using another XML-reader that told me on what lines there were problems... they had use some special symbols in the names that it didn't want to read.

"Content.Shipping&Returns" for example, it didnt like the &-sign...

Fine that you find what was the problem.