- From: RICHARD,FRANCOIS (HP-France,ex1) <francois.richard@hp.com>
- Date: Thu, 15 Jan 2004 13:43:32 +0100
- To: 'Martin Duerst' <duerst@w3.org>, 'Tex Texin' <tex@i18nguy.com>
- Cc: "'public-i18n-geo@w3.org'" <public-i18n-geo@w3.org>, "RICHARD,FRANCOIS (HP-France,ex1)" <francois.richard@hp.com>
Hi Martin, Tex, Thanks for your input and sorry for being so late in answering. I will try in this email to take into consideration your suggestions as well as Tex ones. So, I would like to reduce the scope of the FAQ and rephrase it as: "Is it a good idea to put translatable text in Cascading Style sheet (CSS)?" So that the scope is minimum at the beginning, other l10n topics (font, color, ...) are excluded and only CSS techniques to handle text are looked into... If the FAQ answer can apply to more topics and is not specific to translatable text, then we could extend it to more l10n topics. To address Tex's point, although this suggestion is about going the other way round, starting from very specific (text), going to larger scope if possible. /François >-----Original Message----- >From: Martin Duerst [mailto:duerst@w3.org] >Sent: Wednesday, December 17, 2003 5:21 PM >To: RICHARD,FRANCOIS (HP-France,ex1); 'public-i18n-geo@w3.org' >Subject: Re: New FAQ choice > > > >Hello Francois, > >I think this is an excellent choice of topic area! >However, I would suggest to split things up into several >smaller pieces, e.g.: > >- XSLT vs. CSS >- technical aspects vs. design aspects vs. organisatorial aspects >- Text vs. other localization issues >- fixed text (e.g. one stylesheet for each language) vs. more > advanced techniques > >This will make it easier to create an FAQ quickly, will make it easier >for readers to understand a single topic, and will give us other >opportunities for more FAQs. > >Regards, martin. > >At 14:22 03/12/17 +0100, RICHARD,FRANCOIS (HP-France,ex1) wrote: > >>Hi, >> >>Here is the FAQ I chose with Richard's help. >> >From the section "Writing source text": >>QUESTION: "Is it a good idea to put translatable text in >style sheets?" >> >> >> >>Directions for the ANSWER: >> >>Identify type of content to be handled by style sheet: >> - Repetitive. >> - Linguistically independent. >> - Not context sensitive. >> - Examples: Footnotes, headers, >> - ... >> >>Describe general benefits: >> Maintenance, reuse, consistency >> ... >> >>Conditions required: >> - Localize style sheets first >> - Make sure T&L processes and tools handle style sheets >> - ... >> >>Other related topics: >> - That might not be the only data to localize. Font, >>quotes,... might also require l10n. >> - CSS specifications concerned: 'content' property >> - ... >> >> >> >>All input and feedback welcomed. >> >> >>Fran輟is Richard >>Translation and Localization >>HP Content Management Services >>http://easyweb.grenoble.hp.com/globalization/ >>Internal phone: 1386.6144871 >>External: 33 (0)4 76 14 48 71 >
Received on Thursday, 15 January 2004 07:44:20 UTC