internationalisation of larger text/items

[silky]

Hello,

 How do you guys handle this, specifically of large paragraphs of
text? Localisation of controls and other such items (error messages,
etc) is done trivially via the typical approach[1], and currently with
my longer text I take a similar approach, but there are places where I
have long sentences spanning a few paragraphs. Of course, I can simply
either tokenise the text in some form, or just put HTML in the
resource files themselves (Paragraph 1And so on.) but it
feels slightly bad.

 Any thoughts? Clearly, I want to keep all my localisation work in the
one place.

 I suppose my current approach is the most appropriate, but I'd be
interested to know if anyone has spent any significant time working on
a better solution. I'm not completely sure what it could be ...

-- 
silky

Every morning when I wake up, I experience an exquisite joy — the joy
of being this signature.

[1] http://msdn.microsoft.com/en-us/magazine/cc163566.aspx

RE: internationalisation of larger text/items

[Nic Roche]

You can drag and drop full text files from within your project (with
paragraphs, or any mark-up for that matter)  into your resx designer and
reference them through your base (non-culture named) resx file. They will be
linked and as you update the source files the changes will be available
through the culture-aware resources. This has been useful in creating custom
workflows (xml documents) for specific cultures.

-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of silky
Sent: Sunday, 4 July 2010 7:08 PM
To: ozDotNet
Subject: internationalisation of larger text/items

Hello,

 How do you guys handle this, specifically of large paragraphs of text?
Localisation of controls and other such items (error messages,
etc) is done trivially via the typical approach[1], and currently with my
longer text I take a similar approach, but there are places where I have
long sentences spanning a few paragraphs. Of course, I can simply either
tokenise the text in some form, or just put HTML in the resource files
themselves (Paragraph 1And so on.) but it feels slightly bad.

 Any thoughts? Clearly, I want to keep all my localisation work in the one
place.

 I suppose my current approach is the most appropriate, but I'd be
interested to know if anyone has spent any significant time working on a
better solution. I'm not completely sure what it could be ...

--
silky

Every morning when I wake up, I experience an exquisite joy - the joy of
being this signature.

[1] http://msdn.microsoft.com/en-us/magazine/cc163566.aspx