Re: JStock German translation

  • yccheok

    yccheok - 2011-01-05

    By the way, I saw there is some unused language keys (I already remove them). Is there reason they are there?

  • Anonymous - 2011-01-06

    Hi Yan Cheng!

    Thanks for all the information. I'll try and get this to work after the weekend, since I'll be a little busy until then. Remember that we need to go through all language keys with a <???> tag before we go live. The leftover language keys are probably still there because I kept moving the German language file from one release to the next. The file simply retained the old keys I'd suppose. What is different about Mercury, by the way? Have you considered moving the language information out to external .xml files? :-)

    I'd love to try out a CVS to better stay up to date. However, since I'm running Ubuntu now, I need to figure out how to get this set up first :-) Anyone that could help? It's probably a good idea to do more cross-platform testing in general, though. I've found that Java behaves a lot different on Linux compared to Windows. Ubuntu's new input method framework iBus for example has a nasty bug that makes it unusable with Java applications. Unfortunately this doesn't receive enough attention atm. Here is the link to the bug report on Launchpad:

    Glad you're still working actively on JStock. You're right, let's focus on resolving bugs before making bigger changes to the project.

  • yccheok

    yccheok - 2011-01-06

    Hi Stefan,

    In case you are in Linux, the following commands shall be enough to get all the necessary sources.

    $cd ~
    $sudo apt-get install mercurial
    $hg clone
    $hg clone

    Here are the reason why we switch to this modern Mercurial from CVS :

    Ya. I realize <???> problem. I definitely would like to go through a round with you on better English usage. Let me know when you are free to do so. The next version of JStock won't be released so soon. Most probably I would say,  end of February.

    I still remember moving language information as external file (In Java, common practice is that we don't use XML for language file. We use properties file instead), instead of embedded it into application jar file. However, it is not in high priority list, as it is not a show stopper.