Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/12/2015 14:31, Michael Bauer wrote:

1) Orthography
Terrible reason to turn down a project. Most l10n projects LO has invo
lve languages where spelling is a potentially contentious issue.

Nonetheless, every one of the 3,000 languages that have been reduced to
writing has a published dictionary, and grammar. I'll grant that
regardless of which language one is talking about, there will be
contentious issues regarding the accuracy of the book in question.  That
doesn't mean that work on spell checking and grammar checking should not
be done.  It does mean that whoever creates the spell checker and
grammar checker have a hardcopy (paper) copy of the printed dictionary
and grammar checker of the language in question, and understands both
what in the book is contentious, and why it is contentious.

It also means that when automated tools are used to pare out foreign
words, ensure that only foreign words are omitted.  (How many iterations
of the Afrikaans spell checker were needed, before "die" was included in
it? The same thing happens in other languages, but usually aren't as
blatantly obvious omissions to even the most casual user.)

Team Size

Errr no. 1 dedicated localizer is more than enough. 

How many people should be on a team is as dependent on cultural factors,
as it is on practical factors.

The vice of a one-person team, is that there is nobody to hand off
responsibility for the project off to, if the sole team member is no
longer able to work on the project.

The vice of multi-member teams, is death by paralysis. The inability to
come to mutually acceptable solutions, when questions/problems arise.

In the corporate world in Europe and North America, researchers have
found that eight people on a team, is the most effective size, for a
project to be successful.

5) Start with documentation/help
No.It would raise the wrong expectations, if you give the average user
 a screen that says Filte, unless highly cynical, they would expect the
rest in the same lingo too.

a)  The primary issue with translating the help file after the rest of
the UI, is that it does not get done. (Take a look at the number of
localizations of LibO, where the Help file is not translated into the
target language.)

b) By starting with the Help File, one can incorporate it into the
Documentation Work Flow, ensuring the documentation is consistent across
the various mediums.  Otherwise you end up with situations like the US
English, where the written documentation and the help file contradict
each other. Even worse, is when both the built-in help file, and written
documentation are wrong.

As to the Help, who reads the Help? 

The advanced/expert users of the software.

I realize that Apple pioneered "Prohibit documentation wherever and
whenever possible", but all that really results in, is to ensure that
the user is unable to use the product as designed.

its the worst starting point and a soul-destroying task.

It is no more heartbreaking to translate the Help file, as it is to
translate the rest of the UI, or the documentation that is in other
languages, into the target language.

jonathon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWbKT8AAoJEKG7hs8nSMR70CwP/iw5yyVbNkrdwXgDuI9Z7Iw8
IzFJXk1N10uWhorLOKP2oCe/OvHeagLiOsj9vYjnIuFxPV9puHbci/u9GCgt4bYy
ldcOPngm9WzJIvFwoJZkxIFogNjXrYglPmN47ak14dGEjnBsMQUMAIAMcPafx/JL
dnHnDaOKmNFymvztALRMBHhHxHqBkIrZle76sdpkzwpo1ggPAiOe50utBj1sT1qn
V+DsobD3LEX/fDXdUIFoOhsSB4Ko+kVvSrkpnQQvbsPkaj4o/NSw57f5J/JSaOwo
W/l/a+OcqioT04rmBzJTa3PcWXuwPZ5wshpkvSCbFceXrblqd65FqYcehaE8PC3I
KMDX0Ykrwuam24K6OhdCX0Q73Hqn4r5oOJovRcbWi+0lOfIV3/jiQBbdtzFF8ag3
6cB8T8nq4clcxmRv7x7lZEv3t7pkSRs8JbBezCg1sxCQbIplSSI0iWBNi8QxUzFd
Fhqsf7DwPswCtGz+SdGCxPgWpBvJU6+AImjzIoQaccGd8s+RWVzbRIh0lICFtSkp
kfGoqFJI/JZTUY1PtdluqmR6e6xK0SrDBm33Q8doz82nl9IwLmEsX4+PyyDCqNa4
b6LBSmkMHUUGmMpIx8xlwlehGAsgfzTq41gf4Mr0h/kvy+7DQi/I7+trIw1935Y3
61hnROdhTwlO/YYwy5+o
=lj6Q
-----END PGP SIGNATURE-----

-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.