Loading ...
Sorry, an error occurred while loading the content.

R: [pcgen] interface language

Expand Messages
  • TheForken
    Could you send me your cz.properties, just to try some solutions Bye TheForken _____ Da: pcgen@yahoogroups.com [mailto:pcgen@yahoogroups.com] Per conto di
    Message 1 of 6 , Jul 28, 2005
      Could you send me your cz.properties, just to try some solutions



      Da: pcgen@yahoogroups.com [mailto:pcgen@yahoogroups.com] Per conto di
      Inviato: mercoledì 27 luglio 2005 13.32
      A: pcgen@yahoogroups.com
      Oggetto: Re: [pcgen] interface language

      --- In pcgen@yahoogroups.com, "merton_monk" <merton_monk@y...> wrote:
      > --- In pcgen@yahoogroups.com, "mysmacek" <mysmacek@y...> wrote:

      > > - How can I change encoding used to display the strings? The
      > > language is usually (*) encoded in iso-8859-2 encoding, but PCGen
      > > clearly assumes the encoding is iso-8859-1 and hence
      displays "3/4"
      > > instead of "z with hacek" or "o slash" instead of "r with hacek"
      > I don't think any language we've done to date has required anything
      > outside of what we've used. Getting the encoding changed is fine,
      > except it would require someone to make changes to the java code,
      > we'd then need to get updates to the existing language bundles
      > iso-8859-1 encoding works fine in 8859-2 decoders).

      Either you could
      - make the encoding selectable (either in preferences, or in
      the .properties file itself)
      - or you could switch the language files to utf-8 and make PCGEN
      display utf-8 strings.

      No idea what's needed for either of these, I don't know Java, but
      possibly the latter is the Right-Thing-To-Do (tm). Reencoding
      current language files would be then trivial, I think.

      (* actually, thanks to unnamed software monopoly, we have two
      different encodings if we count only those most used in *nix and
      *doze worlds)

      In the meantime, where can I upload the Czech file for review and
      inclusion? Does it have to be complete? I still did not bother to
      translate exception messages, for example.

      > > - there are some hardcoded/untagged (and badly in addition)
      strings like ...

      > From time to time we've had people go through and make
      > things i18n-compliant, but the task is far from complete.
      > If anyone is interested in this task
      > and is even newish to java, it'd be easy to teach them how to make
      > these changes. It's not hard - just time consuming. It's great
      > exposure to java if you're new to it!

      I would gladly help with that, but I have to get PCGEN compile
      first, which I haven't tried yet.

      > Even if the entire GUI is i18n (because internationalization takes
      > long to type!), the ability to translate the data is far more
      > restricted. You could translate the names and descriptions of
      > but the names of the tags, like BONUS: and PREFEAT: and so on
      > be changed. That's a limitation that would require a *lot* of
      > into overcoming, and we're open to suggestion. :)

      My suggestion is don't change that :-). Translated programming
      languages are PITA.


      PCGen's release site: http://pcgen.sourceforge.net
      PCGen's alpha build: http://www.legolas.org/pcgen/autobuilds
      PCGen's FAQ:



      * Visit your group "pcgen <http://groups.yahoo.com/group/pcgen> " on
      the web.

      * To unsubscribe from this group, send an email to:

      * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
      <http://docs.yahoo.com/info/terms/> .


      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.