Axel Hecht
2018-09-09 13:49:17 UTC
Hi,
tl;dr: If you're not running compare-locales yourself, you can stop
reading. If you don't run it on more than one project at a time, you can
stop reading.
I'm currently making the output of compare-locales more useful in
general, and I'm hitting a point where I'd like to ask a question about:
compare-locales _configs/browser.toml _configs/mobile-android.toml
l10n-central ab-CD
By default, this shows the data for Firefox and then for Fennec. If you
specify --unified, it shows them as one output, but you can't tell if a
file is needing l10n to fix Firefox or Fennec. They're also showing a
summary in each block.
Is anybody using the non-unified output, and if so, intentionally? If
so, the file log or the summary or both?
If I can drop the difference between unified and not, adding
--obsolete=no will be a bit easier ;-)
Axel
tl;dr: If you're not running compare-locales yourself, you can stop
reading. If you don't run it on more than one project at a time, you can
stop reading.
I'm currently making the output of compare-locales more useful in
general, and I'm hitting a point where I'd like to ask a question about:
compare-locales _configs/browser.toml _configs/mobile-android.toml
l10n-central ab-CD
By default, this shows the data for Firefox and then for Fennec. If you
specify --unified, it shows them as one output, but you can't tell if a
file is needing l10n to fix Firefox or Fennec. They're also showing a
summary in each block.
Is anybody using the non-unified output, and if so, intentionally? If
so, the file log or the summary or both?
If I can drop the difference between unified and not, adding
--obsolete=no will be a bit easier ;-)
Axel