Hi,

I've added documentation regarding the homepage management in
doc/devguide/HOMEPAGE. This covers also how translating should
be done.

For volunteers who would like to translate the homepage or just
parts of it, here's the relevant excerpt:

3. Translation

  After you have checked out "htdocs" from CVS, create a new directory
  below "files/" with the ISO 639 code of the target language as name.
  The files to translate are in "files/en/". The files "intro" and
  "sidenav" should be translated first because these are what a visitor
  sees immediately when he enters the homepage. You don't need to
  translate the news_<number> files because they cover mostly old news.
  If you translate them nonetheless, translate the newest first. Some
  files contain information that is only interesting for developers. As
  developers are required to understand English, these files should be
  translate at last - if at all. Information that is interesting for the
  common user has priority.

  Copy only those files from "files/en/" that you actually translate.
  You can translate single files and submit them, the script falls back
  to the original English file if the translation is missing. You may
  make some changes to the HTML code if required for the language (due
  to very long lines or whatever) but in general the document structure
  should be kept as-is. The translation does not have to be 1:1, it
  should capture the intention and spirit of the original English text.
  Sometimes translation shows that the original text is sub-optimal. In
  such a case you should also modify the orignal text instead of
  translating it as-is. All documents must be UTF-8 encoded. If your
  editor does not support UTF-8 properly convert the files manually:

    $ mv file file.bak
    $ iconv -f <Your charset> -t UTF-8 file.bak > file

  To submit translations, use the SF interface:

    https://sf.net/tracker/?atid=304467&group_id=4467&func=browse

  This requires a SF account. As an alternative, simply send a mail to
  the developers' mailing list:

    gtk-gnutella-devel at lists.sourceforge.net

  If you're not subscribed to this list, your mail has to be approved
  by a list moderator which may cause some delay. You can view the archive
  and subscribe here:

      https://lists.sf.net/mailman/listinfo/gtk-gnutella-devel

  If your translated files are larger than a few kilobyte, don't send
  them directly to the list. Provide a URL to the files or ask to whom
  to send the files. Send them to the developer that answers you.

The complete document can be read here:
<http://cvs.sf.net/viewcvs.py/*checkout*/gtk-gnutella/gtk-gnutella-current/doc/devguide/HOMEPAGE>

Note: It'll take a few hours from now before the above link works.

-- 
Christian

Attachment: pgp6Zrf8n0stU.pgp
Description: PGP signature

Reply via email to