i18n pot file

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • anabell

    i18n pot file

    Hi, I'm trying to localize to Chinese language. In the pot file header,
    there appears:

    "POT-Creation-Date: Thu Oct 16 17:07:14 2003\n"
    "PO-Revision-Date: 2003-10-16 HO:MI+ZONE\n"
    "Last-Translator: Anabell chan <achan@mail.des ign.com>\n"
    "Language-Team: LANGUAGE <LL@li.org>\n "
    "MIME-Version: 1.0\n"
    "Content-Type: text/plain; charset=CHARSET \n"
    "Content-Transfer-Encoding: ENCODING\n"
    "Generated-By: pygettext.py 1.5\n"

    What should i fill in the 'CHARSET' and 'ENCODING' ?

  • P@draigBrady.com

    #2
    Re: i18n pot file

    anabell wrote:[color=blue]
    > Hi, I'm trying to localize to Chinese language. In the pot file header,
    > there appears:
    >
    > "POT-Creation-Date: Thu Oct 16 17:07:14 2003\n"
    > "PO-Revision-Date: 2003-10-16 HO:MI+ZONE\n"
    > "Last-Translator: Anabell chan <achan@mail.des ign.com
    > <mailto:achan@m ail.design.com> >\n"
    > "Language-Team: LANGUAGE <LL@li.org <mailto:LL@li.o rg>>\n"
    > "MIME-Version: 1.0\n"
    > "Content-Type: text/plain; charset=CHARSET \n"
    > "Content-Transfer-Encoding: ENCODING\n"
    > "Generated-By: pygettext.py 1.5\n"
    > What should i fill in the 'CHARSET' and 'ENCODING' ?[/color]

    It depends. The best CHARSET to use is UTF-8
    but of course you have to enter UTF-8 data into
    the po file. You can write all languages in UTF-8.
    There are charsets specific to language (groups)
    which you may prefer. For e.g.
    Big5 for traditional chinese
    gb2312 for simplified chinese
    ISO-8859-15 for western European languages

    The ENCODING should be 8bit in all cases

    The handiest thing to do is to look at examples:


    Maybe you could even practice on my application :-)


    Pádraig.

    Comment

    • Radovan Garabik

      #3
      [OT] Re: i18n pot file

      P@draigbrady.co m wrote:[color=blue]
      >
      > It depends. The best CHARSET to use is UTF-8
      > but of course you have to enter UTF-8 data into
      > the po file. You can write all languages in UTF-8.[/color]

      of course, strictly speaking this is not true.
      There are languages with scripts not
      included into unicode yet (such as Old Slavic
      glagolitic script), or languages already rejected
      from unicode (e.g. Klingon script)...
      Just nitpicking.


      --
      -----------------------------------------------------------
      | Radovan Garabík http://melkor.dnp.fmph.uniba.sk/~garabik/ |
      | __..--^^^--..__ garabik @ kassiopeia.juls .savba.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!

      Comment

      Working...