Nick,
yes, I think it should be something like that. I didn't look deeper into it. But there is a already stuff to have multiple documents. If there is a default for locale than it would be the same as it is now. The additional locales would be an extension to the existing structure. This way you could also just use it if you don't care about i18n.
Having multiple pages is not the only thing you probably need. I think having the gettext approach would also be really helpful. Especially if your doing components you could have another source of i18n capability. The synthesis of both could be some kind of markup for enabling the gettext style inside a page.
Norbert
Am 28.07.2011 um 18:28 schrieb Nick Ager:
Hi Norbert,
I haven't attempted any i18n in Pier, though I wonder if it would make sense to modify PRCase to store a Dictionary of PRDocuments keyed by language rather than the single document used in the current implementation.
Nick
On 27 July 2011 17:54, Norbert Hartl
<[hidden email]> wrote:
Does anybody of you use pier with a multilingual setting? If so I would be interested what approaches you take.
I started simple and provided a kernel for each language where the language independent stuff is shared. But the more components I embed the more the whole thing becomes a drag.
So I am very interested in any approach you tried (even if you failed)
thanks,
Norbert
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Locked
