It will be better to handle Android Impress Remote localization
independent of the big LibreOffice source tree. Instead of
stringex, we will use android2po, a 3rd party utility for conversion
strings.xml <-> pot/po.
Change-Id: I4eae53e4f8d94c55e5564d54c5e5c214bc9569d7
Pootle has many checks, but there are cases which are not covered.
Therefore I wrote a tool which checked three types of translation
errors:
1. Unique style names.
2. Unique spreadsheet function names.
3. Missing trailing '|' in Windows installer translation.
Usage: make cmd cmd=solver/*/bin/pocheck
It checks all languages and prints the report to stdout.
Change-Id: I89aad66ea41c0ebe4a6f45beaaf86afd1a6439cc
Now we build only what we really need for 'build' platform - there is
new build-tools make target.
The list of tools is in solenv/gbuild/extensions/pre_BuildTools.mk.
Also similar is done to some extent for 'host' platform using
gb_Module_add_targets_for_build which is ignored for 'host'.
Change-Id: I6acd1762b16aca366aac1a0688500f27869cfca2
Which localize and update help tree files
instead of update_tree.pl.
Use it to update extensions' help.
Next step: use it with general help.
Change-Id: Ife9696bdd8b973ef3cf30626533e38720408179b
Changes:
-Use same methods and commandline params
as other localizers
-Work with one lang during mergeing
-Work well with comments
-Correct makefiles according to one lang concept
Plus delete propex.bat to avoid conflicts
Change-Id: Ia9d2886db263c31f29692c3f6da2b8ec6542b564
we may want to use syntax highlighter class from svtools later,
which is not available for l10ntools
Change-Id: I5a06b77cb6935e3ef68015fb608aa26ac7c53fac
Extract strings from source directly to pot files
Implement PoHeader and PoEntry classes
Renew fomrat of pot/po files
Implement conversion from old po to new po
Change-Id: I411b6041f7d525e76b189d7f31adc5b9ab60f6d6
Reviewed-on: https://gerrit.libreoffice.org/506
Reviewed-by: Andras Timar <atimar@suse.com>
Tested-by: Andras Timar <atimar@suse.com>
So dictionaries is again a nice data-only module and we do not need to
build it in build phase of cross-compilation. It really does not make
sense to build a gazillion of extensions just because we will need one
tiny tool later...
Change-Id: I23f01b818afba1bc8cc88ef3e8305ecfb7a193c0
