I've just translated NewsArticles into Spanish (and will post the files when it's a little more polished).  There were a couple of minor problems which I'll post, but I just have to vent about templates - yaaa!   We finally have a great framework in DNN 3.0 which supports localization.  And while the excellent NewsArticles supports this, templates blow it away with it's use of non-localizable text.

With new modules around for language selection and dynamic content there are going to be more sites out there that want to switch languages within the portal.

I know I can create a template for each language, but now News Articles is the only part of my site that doesn't change when the user's language does and, short of creating a portal per language, I don't see a way round it.

It's not going to stop me using the module and templates are a great extension, but it just doesn't look good on the site.

Thanks for the suggestions. What would work best in your scenario,

Templates with a different locale? e.g. default_DE-de

OR

Tokens in the same template [LOCALIZED-STRINGNAMEINLOCALEFILEHERE]

I have published an article that describes the necessary steps to use almost transparent content localization with News Articles. The site is actually using this setup.

Read it here

Phillipp, I've checked out your site and it looks like a good solution.  I use Erik's modules as well and I just hadn't realised the potential of hiding pages.  I'm going to use this approach on my site!

In answer to the template localization approach - my vote would be for Tokens.  I assume that the strings could then be translated using the language options within DNN - all in one place. 

I don't think it's the existing tokens that are the problem, it's the bits of text that go around them e.g.

Pages: [PAGECOUNT]

"Pages" would need to be localized, so something like this:-

[LOCALIZED-PAGES]

This would look in the resx file (that would be attached to the template) for the key "pages" and extract its value

I have to admit that I never really understood the new concept of using templates in so many modules these days...

Dnn comes with localization and this not only gives great flexibility for static content but also for use as templates. Scott, your example shows a (in my opinion) quite expensive track to take:

1. Look for the string in the template
2. Replace Article tokens
3. Look for localized strings
4. Replace them via GetString with values from the resource files

So why not simply use ONLY resource files? You could skip the whole template thing by keeping the functionality PLUS adding an easy way of localizing the templates.

My 2 cents.

Well, if you have look at the GetSystemMessage method, that is used to e.g. send email notifications in dnn, it does exactly what is being done with templating systems. The difference is that the text string where tokens are being replaced comes from a localization resource file.

The advantage is that this way templates can be modified with the language editor of the portal.

Hi,
Another year, another subscription, another multi-language site to build.  Some great new features for sure but still those annoying little unlocalizable texts in templates.

It would great to have locale specific articles - that would be the icing on the cake  For now I'd just like to have a consitent framework based on my Users selected locale - it just looks tatty for a Spanish user to see bits of English dabbed around the screen or vice-versa.

Locale specific templates would do the job - all the flexibility of templates is retained.  Would Latest Articles get a template as well?