Congegni/sintonia
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

change "Airtime" to "Libretime" except where it refers to code.

Browse source
This commit is contained in:
greenjon 2019-01-22 22:14:59 -08:00
parent ccdd447ddc
commit 126288af6e
9 changed files with 44 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/manual/interface-localization/index.md
View file

@ -1,10 +1,10 @@
The Airtime administration interface can be localized using the standard GNU **gettext** method. Using GitHub for this task means you don't have to tackle the whole of a localization yourself; just as much as you can manage.
The Libretime administration interface can be localized using the standard GNU **gettext** method. Using GitHub for this task means you don't have to tackle the whole of a localization yourself; just as much as you can manage.
![](static/Screenshot464-Korean_stream_setting.png)
First, you should check if a localization is already under way for your locale of choice. The best way to do this is to take a look at the 'master' branch in the GitHub repository for Airtime at <https://github.com/sourcefabric/Airtime/tree/master>. You can also ask in the Airtime development forum at <http://forum.sourcefabric.org/categories/airtime-development>, where you might find community members who can help you with the translation.
First, you should check if a localization is already under way for your locale of choice. The best way to do this is to take a look at the 'master' branch in the GitHub repository for Libretime at <https://github.com/LibreTime/libretime>. You can also ask in the Libretime development forum at <https://discourse.libretime.org/>, where you might find community members who can help you with the translation.
GNU **gettext** means using a .po file for each language or dialect, a specially formatted plain text file with groups of three or more lines, like this example from Airtime's Korean localization:
GNU **gettext** means using a .po file for each language or dialect, a specially formatted plain text file with groups of three or more lines, like this example from Libretime's Korean localization:
#: airtime_mvc/application/configs/navigation.php:57
msgid "Media Folders"
@ -16,11 +16,11 @@ If you use the cross-platform program **Poedit** (<http://www.poedit.net/>) to e
Before manually translating strings in Poedit from scratch, you should take a look at the online translation services available, such as Lingohub (<https://lingohub.com>) or Google's Translator Toolkit (<http://translate.google.com/toolkit/>), which both support gettext .po files. If using automatic translation, you can then use Poedit to fine-tune the localization and fix any formatting errors.
If you don't already have a GitHub account, you can sign up at <https://github.com/signup/free>. Once you have a GitHub account, you can fork a copy (<https://help.github.com/articles/fork-a-repo>) of the Airtime project. Work for the next major version of the software is done in the **master** branch of each project, so that's the branch to **checkout** after you have made the initial **git clone**.
If you don't already have a GitHub account, you can sign up at <https://github.com/signup/free>. Once you have a GitHub account, you can fork a copy (<https://help.github.com/articles/fork-a-repo>) of the Libretime project. Work for the next major version of the software is done in the **master** branch of each project, so that's the branch to **checkout** after you have made the initial **git clone**.
In the locale code *de\_CH*, for example, *de* represents the German language and the suffix *\_CH* indicates the dialect spoken in Switzerland. Some languages have a wide variety of dialect localizations, which can be differentiated with a suffix in this way. You should update the header information in the .po file, which includes the language code and a country code, using one of the existing .po files as a guide.
After forking the Airtime git repository, make sure you're in the **master** branch:
After forking the Libretime git repository, make sure you're in the **master** branch:
git branch
devel
@ -40,18 +40,18 @@ and update the header information in the new copy of the *airtime.po* file using
For the example of Swiss German, the header of the file should now look like this:
# SWISS GERMAN (de_CH) translation for Airtime.
# SWISS GERMAN (de_CH) translation for Libretime.
# Copyright (C) 2013 Sourcefabric
# This file is distributed under the same license as the Airtime package.
# This file is distributed under the same license as the Libretime package.
# Sourcefabric <contact@sourcefabric.org>, 2013.
#
msgid ""
msgstr ""
"Project-Id-Version: Airtime 2.5\n"
"Report-Msgid-Bugs-To: http://forum.sourcefabric.org/\n"
"Project-Id-Version: Libretime 3.0-Alpha\n"
"Report-Msgid-Bugs-To: https://discourse.libretime.org/\n"
After using an online translation tool to begin a new localization, you can load the exported .po file into Poedit and complete your translation there. Enter the localization team's contact information and language into Poedit's **Edit -&gt; Preferences** and **Catalog -&gt; Settings** dialogs, which will be added to the .po file. When you save a .po file in Poedit, the corresponding binary .mo file will be compiled automatically.
Finally, **git add**, **git commit** and **git push** these new .mo and .po files to your GitHub fork of the project, and send a git pull request (<https://help.github.com/articles/using-pull-requests>) to the Airtime developers. The localization can then be added to a forthcoming Airtime release.
Finally, **git add**, **git commit** and **git push** these new .mo and .po files to your GitHub fork of the project, and send a git pull request (<https://help.github.com/articles/using-pull-requests>) to the Libretime developers. The localization can then be added to a forthcoming Libretime release.
If you don't want to work with git, that's no problem - download a copy of the .po template file, edit the header, run it through an automatic translator and check it with Poedit. Then email your contribution to the Airtime team as an attachment - it will be very welcome! However, learning to use git is a good idea, because it means you can work directly on the current source code, share the localization work with the Airtime community, and avoid duplicated effort.
If you don't want to work with git, that's no problem - download a copy of the .po template file, edit the header, run it through an automatic translator and check it with Poedit. Then email your contribution to the Libretime team as an attachment - it will be very welcome! However, learning to use git is a good idea, because it means you can work directly on the current source code, share the localization work with the Libretime community, and avoid duplicated effort.