I beg to differ. All one requires to localize something like LO are
translation skills and a good understanding of how a UI works. Sure, you
need to learn what a placeholder is but that aside, the translation itself
requires much less in the way of IT skills than most projects assume.
A translator needs to know basic concepts of math, finance,
statistics, 3D graphics, programming, typography -- just to name a few
-- in order to translate LibreOffice UI. Even Bugzilla is mentioned in
the README, see
https://translations.documentfoundation.org/gd/libo_ui/translate.html#unit=29478798
How could one translate this sentence without knowing how to file a
bug?
I had, in fact, tried to join OO/Mozilla on my own previsouly but I don't
think people who have been doing this a long time or who do this
profesionally realise how unnecessarily high the hurdles are for "just
translators". You ("we" by now I guess) are all very friendly and helpful,
I'm not suggesting the opposite for a second - but when you're so wound up
in something it's easy to forget what it's like for someone outside the
bubble.
I agree with you in general. Translation should be as easy as possible
(thus we use Pootle, and translators don't have to learn git magic).
But N'ko is a difficult case, because it uses a special script, so
adding it requires more effort, than adding a language that uses Latin
script.
Best regards,
Andras