[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    News from the i18n server
From:       "Thomas Diehl" <thd () kde ! org>
Date:       2000-01-11 9:11:40
[Download RAW message or body]

Hi everybody,

There are a few announcements to make:

=================
Translation Howto
=================

As promised, the intro at http://i18n.kde.org/translation-howto/ has
been updated and should reflect the recent status of all things i18n,
at least for the next few days...;) See the attached table of contents.

There were a lot of changes throughout. I would ask everybody to look
at least into the sections on "Bug Reports" and "Web Site Translation".
Inclusion of translation problems into the KDE bug tracking system is
still under construction, not yet implemented.

A .tgz archive and a PDF version (from the HTML version) are included
this time. Also the DocBook source, mainly for the people who asked me
about translating the document for their teams. As for contributions
and corrections I would prefer that people mail them to me for
incorporation into the document.

BTW: Wolfram Diestel has written a very interesting Howto on Unicode
(for developers mainly). See
http://developer.kde.org/kde2arch/KDE-Unicode-Howto.html

==========
Tools Page
==========

Matthias Kiefer has moved the home pages of KBabel and kdedict to the
server, see http://i18n.kde.org/tools/ (for users of the i18n CVS:
there is an extra "tools" module for these). Everybody is invited to
contribute scripts, programs, whatever that could be of practical use
for KDE translators and documenters.

=========
Snapshots
=========

Stephan Kulow is in the process of fixing the reported problems with
configure in http://i18n.kde.org/translation_archive/

======
WebCVS
======

There were a lot of complaints about the WebCVS at fh-heilbronn.de not
being updated properly any more. Don't know if this has improved since.
Anyway, http://www.nebsllc.com/cgi-bin/cvsweb.cgi/ was recommended as a
good alternative.

Kind regards,

Thomas



--------
Table of Contents
1. Introduction
2. Bringing a New Language to KDE
    2.1. First Things First...
    2.2. Taking a Look at Available Resources and CVS
    2.3. Starting the Actual Translation
    2.4. Localization Issues
    2.5. Where to Go From Here: Some Practical Hints
3. GUI Translation
    3.1. POT and PO Files
    3.2. To-do Lists for GUI Translation
    3.3. Step by Step: The Translation of POTs and POs
    3.4. Peculiarities and Difficulties
    3.5. Using Specialized Programs for GUI Translation
       3.5.1. KTranslator
       3.5.2. KBabel
       3.5.3. (X)Emacs in PO Mode
    3.6. Checking and Committing Your Work
       3.6.1. Syntax Check: msgfmt --statistics
       3.6.2. Compilation and Context Check
       3.6.3. Committing Your Work to CVS
4. Doc Translation
    4.1. SGML Files: DocBook Versus HTML and LinuxDoc
    4.2. Setting up a Working Environment
    4.3. To-do Lists for Doc Translation
    4.4. Step by Step: The Translation of DocBook SGML files
    4.5. Pecularities and Difficulties
    4.6. Using Specialized Programs for Doc Translation
       4.6.1. (X)Emacs in SGML Mode
    4.7. Checking and Compiling Your Work
       4.7.1. Syntax Validation and Proof-reading
       4.7.2. Compilation of Translated Documentation
5. Bug Reports and User Feedback: Handling and Translating
    5.1. Handling Translation Bugs
       5.1.1. Submitting Bug Reports
       5.1.2. Closing Bug Reports
       5.1.3. Followup Messages
    5.2. Handling Non-English User Feedback
6. Web Site Translation and Design
    6.1. Web Sites for Internal Use
    6.2. Web Sites for KDE Users
7. Appendix: Tools and Resources for KDE Translators
    7.1. The i18n Server
    7.2. CVS, CVSUP, WebCVS...
    7.3. Mailing Lists, IRC, and On-line Fora
    7.4. Web and FTP Sites
    7.5. Files
    7.6. Statistics
    7.7. HOWTOs
    7.8. Specialized Programs and Modules
       7.8.1. ...for GUI Translation
       7.8.2. ...for Doc Translation
    7.9. Dictionaries and Tools for Consistency Checking
8. Acknowledgements

[prev in list] [next in list] [prev in thread] [next in thread]