[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFC] i18n and documentation

On Fri, Jun 14, 2002 at 12:40:44AM +0200, Denis Barbier wrote:
> [Reply-To: d-i18n, Cc: d-doc from which this discussion comes from]
> Hello,
> the intro-i18n document explains what i18n does mean for programs,
> but it does not cover documentation.  Having guidelines for
> documentation writers to help translators would be of great help,
> so let's gather some ideas.
> I will present here a translator's (and revierwer's) view.  If we
> agree on what he needs to perform his job, we can deduce what features
> l10n tools should provide, and how docs should be written to help
> translators.
> Examples at bottom illustrate these points.
> A.  Requested features
> ======================


>   3) Support for any encoding
>      ------------------------

EBDIC, anyone? :-)

this need to be clarified - e.g., for Slovak, nobody needs to 
support microsoft CP1250 codepage. But for Bulgarian, commonly used
linux encoding is Microsoft CP1251, even though KOI8-R or ISO-8859-5
would be expected.

| Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik/ |
| __..--^^^--..__    garabik @ melkor.dnp.fmph.uniba.sk     |
Antivirus alert: file .signature infected by signature virus.
Hi! I'm a signature virus! Copy me into your signature file to help me spread!

To UNSUBSCRIBE, email to debian-doc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: