Different people use different expressions but mostly people use quite a selection. "Must be" is
typically used by people in power (such as parents, my boss, the prime-minister etc) but who might
lack the imagination to realise there might well be some other way that they haven't thought of.
"What is usually used?" is a bit like asking what the best distro is. Each person has their own
idea and those ideas might change from moment to moment. It's hard to avoid being flippant when
answering this sort of thing.
Also once i am "on a roll" and writing quickly i sometimes find i have repeated a word or phrase
many times, sometimes even with a single sentence. It's a bit like tripping over my own shoelaces
in haste or finding i tied them together. So it's not always arrogance that leads to that sort of
3. I quite like "with the same text". It still avoids the problem Sophie made me aware of. So;
There should not more than one entry with the same text in the help directory because it will break
the index display in the help UI.
or the re-write i did later, or some variant of it.
Wrt tags/options and stuff. I am disappointed to hear they are not translated and set by
regionalisation. For some reason i had assumed that people could use the command-line in their own
On Sunday, 13 October 2013, 15:44, Thomas Hackert <email@example.com> wrote:
Hello Tom, *,
On Sonntag, 13. Oktober 2013 12:54 Tom Davies wrote:
I tend to dislike "must not" too. It's soo authoritarian that it
makes me want to go against it or to find out why not by
experimentation. I prefer things like; should avoid try not to
it's worth avoiding ... because ...
and other such less definite equivalents. Even better is if you
can flip it around to say the positive instead.
just out of interest (as you have not written something about it):
What is usually used in English?
3. Looks clunky. I do prefer the 3rd way of writing it but can
now see the problem that Sophie was trying to avoid. Perhaps
<quote> There should not more than one entry with the same
contents in the help directory because it will break the index
display in the help UI. </quote> Perhaps instead of "contents" it
might be better to use another word such as; text, value, errr i
can't think of others but maybe Anne-ology might know a much
Than I would prefer "with the same text" ... ;)
In 5 & 6 i agree with Sophie. It is less elegant but is less
likely to create confusion. When a number of tags get combined
(as in "-rin") it almost looks like a word that might need to be
translated whereas separately they are clearly tags/options.
People probably wouldn't try to translate "-r -i -n".
Just out of interest: Why would you translate parameters, options
(and the like) of an command (or the name of it itself)?
There are tags that are entire words and those might need
Why? Usually the command itself as well as its parameter, options
and the like are – IIRC – never translated. It is something
completely different with its help, manpages, info and the like,
but I may be wrong here ... ;)
for example with the rsync command there is
"--partial" and "--progress" but a) Those have a double "-" sign
b) Only translate if the under-laying OS is in a non-English
language and only if the particular command has been translated
There are too many ifs there so it's probably worth avoiding those
sorts of tags
On my system (Debian Testing AMD64), neither of them is translated.
Also its help text is in English here, although I have installed
with locale "de_DE.UTF-8" ... ;)
7 "Escape character" might be written as "escaping character"
without changing the meaning. The grammar of the sentence might
require an "ing", or else the term would need to be defined. Devs
and coders might have a more precise meaning for the term but i
think the usage is sufficiently close and is readily understood by
normal users without explanation.
It is good to learn about built-in help available on the
command-line and easy to look-up without going off and opening a
web-browser but i agree with Sophie that it is all really a
subject for other books and faqs and there are plenty of them
already! People still don't know all about all this and there is
no reason they should. I hadn't known of "info" until this post
so thanks for that! :)
You are welcome :)
I generally use "--help" or "-h" to get a
Me too, but sometimes it is not that informative or misses some "use
case" examples ... And then I find "man $program" or "info program"
faster than switching to another workspace, start a browser (or if
it is started already, to open a new tab) ... ;)
The "man" pages give a LOT more detail but it's awkward to keep
them open while typing on the command-line itself (unless you open
it in a new windows or tab).
This is, how I do it: Try $program in one tab of konsole and if I
want to know something, I press <Ctrl>+<shift>+<T> to open a new
tab, enter "man $program" (or "info $program"), read through it (or
if I want to do something special, then I press "/" to search the
manpage, enter – say I want to find out, if it is possible to copy
something – "copy" and read it there ... ;)
Also it took me ages to realise that
it was a "vi" editor and that i could escape by using
He he, reminds me on my first experiences with the command line ...
before that i was a bit stuck because even "Ctrl c" wouldn't get
me back to the command-line and i'd have to close the "terminal
console" / "command-prompt window". Now i know about ":q" it's
easier for me.
And do not forget ":wq" to save before closing ... ;)
Anyway, nicely done! Especially with 3. That was a good catch :)
Thank you :)
<Rest snipped and TOFU removed, see
Basically my wife was immature. I'd be at home in the bath and she'd
come in and sink my boats.
-- Woody Allen
To unsubscribe e-mail to: firstname.lastname@example.org
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
Re: [libreoffice-l10n] Documentation for l10n · Leo Moons
- Re: [libreoffice-l10n] Documentation for l10n (continued)
Impressum (Legal Info)
: 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