aboutsummaryrefslogtreecommitdiffhomepage
path: root/TRANSLATION.md
diff options
context:
space:
mode:
authorJeremy Benoist <j0k3r@users.noreply.github.com>2016-01-15 16:29:06 +0100
committerJeremy Benoist <j0k3r@users.noreply.github.com>2016-01-15 16:29:06 +0100
commit3bcc4d4cb29abeedb48b1f297f1a65a02998ff69 (patch)
tree78675c7bdbfbf252eff9c8bc6328f44d3db9bb31 /TRANSLATION.md
parentf902d7815326e81913904257cc4485b4dfef5d13 (diff)
parent160e2d8f0b1e4c3e9fe7f89300de22c5ef334833 (diff)
downloadwallabag-3bcc4d4cb29abeedb48b1f297f1a65a02998ff69.tar.gz
wallabag-3bcc4d4cb29abeedb48b1f297f1a65a02998ff69.tar.zst
wallabag-3bcc4d4cb29abeedb48b1f297f1a65a02998ff69.zip
Merge pull request #1584 from wallabag/v2-cleanup
some cleanup
Diffstat (limited to 'TRANSLATION.md')
-rw-r--r--TRANSLATION.md67
1 files changed, 0 insertions, 67 deletions
diff --git a/TRANSLATION.md b/TRANSLATION.md
deleted file mode 100644
index a033662c..00000000
--- a/TRANSLATION.md
+++ /dev/null
@@ -1,67 +0,0 @@
1# How to manage translations for wallabag
2
3This guide will describe the procedure of translation management of the wallabag web application.
4
5All translations are made using [gettext](http://en.wikipedia.org/wiki/Gettext) system and tools.
6
7You will need the [Poedit](http://www.poedit.net/download.php) editor to update, edit and create your translation files easily. However, you can also handle translations also without it: all can be done using gettext tools and your favorite plain text editor only. This guide, however, describes editing with Poedit. If you want to use gettext only, please refer to the xgettext manual page to update po files from sources (see also how it is used by Poedit below) and use msgunfmt tool to compile .mo files manually.
8
9You need to know, that translation phrases are stored in **".po"** files (for example: `locale/pl_PL.utf8/LC_MESSAGES/pl_PL.utf8.po`), which are then complied in **".mo"** files using **msgfmt** gettext tool or by Poedit, which will run msgfmt for you in background.
10
11**It's assumed, that you have wallabag installed locally on your computer or on the server you have access to.**
12
13## To change existing translation you will need to do:
14
15### 1. Clear cache
16You can do this using **http://your-wallabag-host.com/?empty-cache** link (replace http://your-wallabag-host.com/ with real url of your wallabag application)
17
18OR
19
20from command line:
21go to root of your installation of wallabag project and run next command:
22
23`rm -rf ./cache/*`
24
25(this may require root privileges if you run, for example Apache web server with mod_php)
26
27### 2. Generate php files from all twig templates
28Do this using next command:
29
30`php ./locale/tools/fillCache.php`
31
32OR
33
34from your browser: **http://your-wallabag-host.com/locale/tools/fillCache.php** (this may require removal of .htaccess file in locale/ directory).
35
36### 3. Configure your Poedit
37Open Poedit editor, open Edit->Preferences. Go to "Parsers" tab, click on PHP and press "Edit" button. Make sure your "Parser command:" looks like
38
39`xgettext --no-location --force-po -o %o %C %K %F`
40
41Usually it is required to add "--no-location" to default value.
42
43### 4. Open .po file you want to edit in Poedit and change its settings
44Open, for example `locale/pl_PL.utf8/LC_MESSAGES/pl_PL.utf8.po` file in your Poedit.
45
46Go to "Catalog"->"Settings..." menu. Then go to "Path" tab and add path to wallabag installation in your local file system. This step can't be omitted as you will not be able to update phrases otherwise.
47
48You can also check "project into" tab to be sure, that "Language" is set correctly (this will allow you to spell check your translation).
49
50### 5. Update opened .po file from sources
51Once you have set your path correctly, you are able to update phrases from sources. Press "Update catalog - synchronize it with sources" button or go to "Catalog"->"Update from sources" menu.
52
53As a result you will see confirmation popup with two tabs: "New strings" and "Obsolete strings". Please review and accept changes (or press "Undo" if you see too many obsolete strings, as Poedit will remove them all - in this case please make sure all previous steps are performed w/o errors).
54
55### 6. Translate and save your .po file
56If you have any difficulties on this step, please consult with Poedit manual.
57Every time you save your .po file, Poedit will also compile appropriate .mo file by default (of course, if not disabled in preferences).
58
59You are now almost done.
60
61### 7. Clear cache again
62This step may be required if your web server runs php scripts in name of, say, www user (i.e. Apache with mod_php, not cgi).
63
64
65##To create new translation
66You just have to copy the folder corresponding to the language you want to translate from, change language in the project settings and for the folder and files names. Then start replacing all existing translations with your own.
67