Ticket #21 (closed enhancement: fixed)

Opened 10 years ago

Last modified 9 years ago

Request: localization

Reported by: zxalexis Owned by: alamaison
Priority: critical (affects core workflow) Milestone: 0.3.2.0 Internationalisation
Component: i18n Version:
Keywords: i18n charset encoding Cc:

Description

The program is very powerful but lacks some things:

  1. Does not have any i18n support (as I know the gettext will be suitable for this - and is compilable in windows)
  2. Does not support changing charset encoding either for the server-side (I do have some FreeBSD machines which are in KOI-8R keymap) and for the client-side (my Win machine uses CP866 for network names - and so are all Russian users have)

as for the first - I could help if asked. zxalexis[at]gmail.com

Change History

comment:1 Changed 10 years ago by alamaison

  • Keywords i18n charset encoding added
  • Status changed from new to accepted

I18n is something I've very keen to add (though I can't give a timeframe for doing so). As you suggest, gettext is the best solution. Once I start i18n I will need help from you and the community, especially with testing and translation.

As for your second point regarding charset encoding, can you explain this problem in more detail and if it's separate from the first point, please file it as a new bug so we can track them separately.

comment:2 Changed 10 years ago by zxalexis

Thanks. I'll be waiting for the .po or .pot to translate)
For the second point created Ticket #22 (with screenshot)

comment:3 Changed 10 years ago by alamaison

  • Priority changed from major to critical
  • Component changed from frontend to i18n
  • Milestone set to 0.3.2.0 Internationalisation

comment:4 Changed 9 years ago by alamaison

  • Status changed from accepted to closed
  • Resolution set to fixed

The translation template (POT) can be found here:  http://swish.svn.sourceforge.net/viewvc/swish/trunk/po/template/swish.pot

Note: See TracTickets for help on using tickets.