[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Re: [Q] multilingual website?
Asunto: [docbook-apps] Re: [Q] multilingual website? Fecha: lun, mar 15, 2004 at 06:44:32 +0100 Citando a Steinar Bang (sb@dod.no): > >>>>> Dave Pawson <dpawson@nildram.co.uk>: > > > I was thinking of taking those ideas and extending to a document content. > > (brain dump) > > > Main document contains structure, and references to the text, and > > the required languages. Format is empty block level elements, with > > perhaps numbered references to simple blocks of text with inline > > markup. > > > The .en or .fr files hold the content, in the appropriate language. > > One, call it the original, is identified, all others are > > translations of that file, with any inline markup. > > Ah. I think I see what you mean. > > > Does the idea make sense? > > Yes. In fact, it's similar to how JSPs handles translations. > > But I don't have the slightest idea where to start digging to > accomplish this. I have to start with that presentation of Norm's you > linked to, I guess. > But I think you don't need only to translate automatically generated text. You need a way (like with gettext tools) to translate __all__ the text (automatic an manual) in your website, don't you? If you use apache, like you suggest, you can think in a way to generate the .po files to translate, but i don't know if it's better to generate from .xml or from .html files (You want to display static content at your website, i think). I think it's a very interesting question. -- lm
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]