• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

LINGUASH A D04-Jan-201612 21

MakevarsH A D04-Jan-20161.1 KiB2923

README.mdH A D04-Jan-20161.3 KiB2620

es.poH A D04-Jan-201611.2 KiB510394

fr.poH A D04-Jan-201610.5 KiB508393

gl.poH A D04-Jan-201611.1 KiB509393

ru.poH A D04-Jan-201612.5 KiB506391

violetland.potH A D04-Jan-20168.6 KiB502387

README.md

1How to add a translation
2========================
3
4In order to enable as many people as possible this the joy of playing Violetland
5we are aming at providing localized versions in all major languages. Since
6creating a complete localization from scratch is a big effort, the preferred way
7is to contribute to the crowdsourced translations on
8[GetLocalized](http://www.getlocalization.com/violetland/).
9
10After a localization is finished, a new language has to be added to `LINGUAS`,
11for example `fr` for "french". A list of supported language codes can be found
12in the [gettext manual](http://www.gnu.org/software/gettext/manual/html_node/Usual-Language-Codes.html).
13
14Now download the appropriate po files from
15[GetLocalized](http://www.getlocalization.com/violetland/files/) and apply the
16necessary adaptions. Most likely you have to rename the file from
17`violetland-<language>.pot` to `<language>.po` and specify [plural
18forms](http://www.gnu.org/savannah-checkouts/gnu/gettext/manual/html_node/Plural-forms.html).
19You may want to use a po enabled editor like [poedit](http://www.poedit.net/) or
20[vim](http://www.vim.org/).
21
22Support for the new language will now automatically be generated at build time.
23To test the new language, you can modify your `LANG` environment variable before
24running `violetland`.
25
26