- From: Martin Duerst <duerst@w3.org>
- Date: Wed, 17 Dec 2003 11:00:27 -0500
- To: "RICHARD,FRANCOIS (HP-France,ex1)" <francois.richard@hp.com>, "'public-i18n-geo@w3.org'" <public-i18n-geo@w3.org>
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 Wednesday, 17 December 2003 11:20:38 UTC