Basically translations are divided into two areas, those that are DNN and/or extensions and then the content.
U can more or less go by the rule, that anything u can edit urself within an extension, will be classed as content in this regard, as if u want it to show in ml, there has to be a feature built in to the extension that allows for ml input.
Then everything u don't have editing access on, like labels, names, titles etc for any given extension, will be translated thru the resource files in DNN.
In some cases u might hit the barrier of no resource file entry for some text or label somewhere, because it was just hardcoded into the extension, that's where u can use extensions like DSLocalizator as itll do translations by replacing words or even complete strings with translated ones.
Also the extension may not have ml support which can be rather annoying if u found just the right extension for the purpose, then DSLocalizator might be the answer.
However string translation thru DSLocalizator can be tricky to manage and it shdnt be used to set up translations for single words, because itll most likely mess up both the translations in general, but also as it translates at HTML level, it means itll translate anything in the HTML that matches and by that it might change things like naming of textboxes, labels, radiobuttons etc. in case theres a match, so limit the use of something like this to a minimum and always do massive testing after implementing translations like those.
I always stick to the resource files as far as possible to avoid errors and then I use the extensions built-in ml support for the content and that way its working very well for me. :-)
Cheers
Jake
U can more or less go by the rule, that anything u can edit urself within an extension, will be classed as content in this regard, as if u want it to show in ml, there has to be a feature built in to the extension that allows for ml input.
Then everything u don't have editing access on, like labels, names, titles etc for any given extension, will be translated thru the resource files in DNN.
In some cases u might hit the barrier of no resource file entry for some text or label somewhere, because it was just hardcoded into the extension, that's where u can use extensions like DSLocalizator as itll do translations by replacing words or even complete strings with translated ones.
Also the extension may not have ml support which can be rather annoying if u found just the right extension for the purpose, then DSLocalizator might be the answer.
However string translation thru DSLocalizator can be tricky to manage and it shdnt be used to set up translations for single words, because itll most likely mess up both the translations in general, but also as it translates at HTML level, it means itll translate anything in the HTML that matches and by that it might change things like naming of textboxes, labels, radiobuttons etc. in case theres a match, so limit the use of something like this to a minimum and always do massive testing after implementing translations like those.
I always stick to the resource files as far as possible to avoid errors and then I use the extensions built-in ml support for the content and that way its working very well for me. :-)
Cheers
Jake