Re: GNU Backgammon Translation into Ukrainian

[Superfly Jon]

Here's some info from the archive from Petr Kadlec:

Gnubg's translation is based on GNU gettext package (see http://www.gnu.org/software/gettext/ for info). In short, you need to take a text file with the translation template and for each english item add its translation.

The template is located in po/gnubg.pot in the source tree (http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/gnubg/gnubg/po/gnubg.pot?rev=HEAD&content-type=text/plain) it is generated automatically from the source files using the gettext tools.

You should be able to update the gnubg.pot file with:

make update-po

Although I haven't tried that...

Jon

On Thu, 9 Mar 2023 at 21:57, Philippe Michel <philippe.michel7@free.fr> wrote:

On Thu, Mar 09, 2023 at 08:45:46AM +0200, Андрій Рак wrote:
> Good afternoon.
> I, EGYT, am from Ukraine and I would like to translate GNUBG into
> Ukrainian. I would be very grateful if I could get a .po file with all the
> text in the game, because the English (US) translation has only 1464 lines,
> while the Finnish translation has 3445 lines, and I'm not sure if these
> 3445 lines are really all the lines in the game. Also, the English (UK)
> translation is only 351 bytes, and doesn't have a single line.

You're welcome to add an Ukrainian translation.

I'm not sure I understand what you mean with the line numbers. The 351
bytes English UK file is the "mo" compiled file, that's not the kind of
file you want to use.

The current po source files are at
https://cvs.savannah.gnu.org/viewvc/gnubg/gnubg/po/

You should probably start with a copy of the en_GB.po file (it contains
no translations since gnubg default is UK English, but the source
strings are there).

Adapt the headers (please use UTF-8, not ISO8859 or KOI8). Maybe copy
the Plural-Forms: from ru.po if the Ukrainian plurals are identical or
use it (or the simpler ones from ro.po or cs.po) as example.

You probably don't want to edit the po file with a standard text editor.
There are specialized ones for this, for instance poedit
(https://poedit.net/)

All current translations except Finnish are far from complete. This is
not critical. It is better to start with the most used parts of the user
interface or the more confusing ones, integrate this in a version you
can check for issues (for instance if the size of the first try of a
translated string is very different from the original one the UI may
look inacceptably wrong) and work incrementally.