[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Re: [Q] multilingual website?
----- Original Message ----- From: "Dave Pawson" <email@example.com> To: "luis miguel morillas" <firstname.lastname@example.org>; <email@example.com> Sent: Friday, March 19, 2004 8:37 AM Subject: Re: [docbook-apps] Re: [Q] multilingual website? > At 19:16 15/03/2004, luis miguel morillas wrote: > >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? > > Yes, for any multi-lingual site. > But having done that, how to manage those translations? > I think that is where Norm and his ideas are very good. > > > If you use apache, > > That is serving the content. > A separate problem? > or do you see that as a part of the transformation, > selecting the presentation language dependant on ... what? I think he means to generate the translated files ahead of time, install them on the server, and allow the server to automatically select the appropriate file. That's why he was asking about generating the different filenames. > How can I tell a users preferred language? > Perhaps some pre-selected option from the web site front page? Apache's language negotation feature is based on the value of the HTTP_ACCEPT_LANGUAGE header that comes in the HTTP request. That header is set by the user's language preference settings on their browser. Bob Stayton Sagehill Enterprises DocBook Consulting firstname.lastname@example.org