Utilities
-typo.php - is a crude syntax checker to avoid checking in files with simple
+php bin/console.php typo - is a crude syntax checker to avoid checking in files with simple
typos. It basically just loads each of our project files at once. Run from
cmdline and see if any parsing errors are reported.
Internationalisation
-php bin/console extract - extracts translatable strings from our project files. It
+php bin/console.php extract - extracts translatable strings from our project files. It
currently doesn't pick up strings in other libraries we might be using such as
the HTML parsers.
Xgettext and .po workflow
-1. Run util/run_xgettext.sh script (on *unix sistems, with GNU xgettext installed)
+1. Run bin/run_xgettext.sh script (on *unix sistems, with GNU xgettext installed)
This script runs xgettext on source tree, extracting strings from L10n::t() and L10n::tt()
functions, and creates a util/messages.po file.
- $ cd util; ./run_xgettext.sh
+ $ cd bin; ./run_xgettext.sh
2. copy util/messages.po to view/lang/<language>/messages.po
Replace <language> with the language you are working on - e.g. 'es', 'fr', 'de', etc.
of the many .po editors out there, like QtLinguist
5. run
- $ php bin/console po2php view/lang/<language>/messages.po
+ $ php bin/console.php po2php view/lang/<language>/messages.po
to create the strings.php file
When strings are added or modified in source, you could run
- $ cd util; ./run_xgettext.sh ../view/lang/<language>/messages.po
+ $ cd bin; ./run_xgettext.sh ../view/lang/<language>/messages.po
to extract strings from source files and join them with the existing .po file:
new strings are added, the existing are not overwritten.
If you already translated Friendica using strings.php, you could import your old
translation to messages.po. Run:
-$ php bin/console php2po view/lang/<language>/strings.php
+$ php bin/console.php php2po view/lang/<language>/strings.php