Translating DAViCal: Difference between revisions

From Davical
Jump to navigationJump to search
(Move from Open to Libre Office)
 
Line 6: Line 6:
Or you can see all of the translation files here: [https://github.com/DAViCal/davical/tree/master/po https://github.com/DAViCal/davical/tree/master/po] and then click on any file and then the {{{raw}}} link to download it.  Each time the strings are updated in the code the new strings will be merged into the existing translations.  
Or you can see all of the translation files here: [https://github.com/DAViCal/davical/tree/master/po https://github.com/DAViCal/davical/tree/master/po] and then click on any file and then the {{{raw}}} link to download it.  Each time the strings are updated in the code the new strings will be merged into the existing translations.  


Save that to a file which you edit in some editor that can to UTF-8, such as VIM, EMacs or [http://www.openoffice.org OpenOffice.org] Writer.  
Save that to a file which you edit in some editor that can to UTF-8, such as VIM, EMacs or [http://www.libreoffice.org LibreOffice] Writer.  


== Editing with Transifex ==
== Editing with Transifex ==

Latest revision as of 21:48, 21 January 2016

Template:Languages If you would like to translate DAViCal into a different language, you can download the language definitions base file from our Git repository here:

The base DAViCal messages.pot file can be fetched from: https://github.com/DAViCal/davical/raw/master/po/messages.pot

Or you can see all of the translation files here: https://github.com/DAViCal/davical/tree/master/po and then click on any file and then the {{{raw}}} link to download it. Each time the strings are updated in the code the new strings will be merged into the existing translations.

Save that to a file which you edit in some editor that can to UTF-8, such as VIM, EMacs or LibreOffice Writer.

Editing with Transifex

Template:TransifexStats

This is probably the easiest method unless you're an experienced translator:

  • Go to the DAViCal project on Transifex and create yourself an account.
  • Request to join a translation team for your chosen language, or to start a new one if there isn't one already.
  • Start translating strings in your language of choice.

Just in case you were wondering, there are some stats over to the right showing what languages are up to date and what ones need work.

Some thoughts about where it is most useful to put in a little effort:

  • Translations showing less than 50% could really do with some help.
  • If you can translate even 10% you can provide useful clues to people who are not able to use one of the more translated languages.
  • Languages that are more than 80% translated are already well served by moderately active translators and need little help.
  • If you're a native speaker, a quick review of the main translators work is always useful.

Transifex CLI and xgettext mini how-to (DEPRECATED)

Editing with VIM

You will need to make sure that you are using UTF-8 encoding, such as by adding this line to your ~/.vimrc file:

set enc=UTF-8

Under Win32 you can use Gvim for windows 7 which has more windows-like keybindings. You'll need to set it to use UTF-8, IIRC. Use Edit|Settings Window to do this. Search for the line containing "set enc="

Alternatively, in Linux, OS X, Windows or anything else, inside GVim you should be able to type {{{:set enc=UTF-8}}} to switch to UTF-8.

Editing with LibreOffice

If you use LibreOffice Writer, you can save the file as "Text Encoded", make sure the "Edit Filter Settings" option is checked and that the file is saved as "UTF-8" with "LF line endings".

Editing with EMacs

If you use Emacs, you can use C-x RET f and specify utf-8 as coding system for saving file.

Other ways of editing this file

If you can tell us how to edit these files in other ways, we would love to know about that too!