On Sun, Oct 17, 2010 at 9:44 AM, Aurimas Fišeras <aurimas@gmail.com> wrote:
2010.10.17 17:15, Norbert Thiebaud rašė:
On Sun, Oct 17, 2010 at 6:35 AM, Aurimas Fišeras <aurimas@gmail.com> wrote:
Fixes more typos in documentation.
Aurimas,
Thanks for the patch.
I partially merged it, based on the following criteria:
1/ we can't have unicode characters in the source code, so I did not
merge "Bézier" which showed up as B<C3><A9>zier. for me.
It's unfortunate, what causes such limitation?
History, the weight of millions of line of existing code, and the fact
that Unicode support is still only recently ubiquitous.
The good news is that ascci being a subset of utf-8, at some point in
the future it might be possible to
switch to utf-8... but the cost/benefit ratio is not in favor of such endeavor
However, it should at
least be "Bezier" with a capital B. I'll fix it later.
Sure.
2/ Some of these correction were a matter of British English vs American English
Yes, I greped all documentation and there were more instances of
American English (e.g. behavior) than British English so I used American
English spelling to be more consistent.
There are files where both spellings are used in the same file. Which
spelling should be used in this case?
As I understand from lack of en-US translation in libreoffice/l10n,
en-US is the primary language of LibreOffice? Documentation should also
be in en-US, shouldn't it?
Honestly I do not have a strong opinion on the matter, and I didn't want
to be the one starting a turf war on english dialect.
3/ Some were neologism that have - in my view anyway - a distinct sens
in the context of computing. prepend for example has a meaning which I
find distinct to prefix (prefix/postfix - prepend/append)
I didn't see any difference between prepend and prefix in that
particular place and replaced it with a more formal "to prefix"
"prepend definition jargon /pree'pend'/ (by analogy with "append") To
prefix or add to the beginning."
However, I will leave the only other place where it is used unchanged ;)
I have only read the change you submitted... so I don't know about the
other places...
It's just that I have used, in API names, the symmetry of append/prepend
(like chaine_append(...) and chaine_prepend(...)) so I can imagine
that the use of prepend _may_ have been intentional.
I also apologized, but I had to submit your contribution under Aurimas
Fiseras, as I was not able to type Fišeras in my console....
;)
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.