nvaccess / l10n-code Goto Github PK

The userGuide-structureDifferences.txt file helps translators ensure that the structure of their translated document matches the English document. Some locales (e.g. Arabic and Hebrew) need to include a locale specific configuration file which sets specific HTML attributes (e.g. lang, dir). Unfortunately, this causes every section to be reported in the structure differences because the lines are offset, even if the overall structure would be identical if the locale include were removed. For example:

# Structural comparison of he/userGuide.t2t against he/userGuide-newRevisions/13103/userGuide.t2t
en 1. start:10 paragraphs:1, tables:0, lists:0
he 1. start:12 paragraphs:1, tables:0, lists:0
en 1.1. start:15 paragraphs:2, tables:0, lists:1
he 1.1. start:17 paragraphs:2, tables:0, lists:1
...
en 15. start:2306 paragraphs:1, tables:0, lists:0
he 15. start:2308 paragraphs:1, tables:0, lists:0
# end of comparison

Ways this could be improved:

1. The locale include should be excluded.
2. Rather than comparing the start line numbers of every section, perhaps a detected offset could be reported but not affect comparison of subsequent sections.

Translators can choose to enable an add-on via their language's settings file so that they will receive material to be translated for that add-on. When the first add-ons are added, the add-ons directory (where the files for translation are placed) will not have been created yet. This causes the addon2svn script to fail for the entire add-on.

Possible solutions:

1. When a language is added to the system, the add-ons directory should be created as part of that process. If we're going to rely on this, we should automate it. (Currently, it's manual.)
2. When an add-on is enabled in settings, the post-commit hook should create the add-ons directory if it doesn't already exist.

nvda2svn is run automatically every Friday. At present, it always changes po files for all languages, even if there are no changed strings. This is due to changes in the date in the file, formatting differences, etc., but these are all purely cosmetic. It should skip the file if there are no real changes.

I believe we already do something similar for addon2svn. The pocount tool will be useful here.