Hello Johnny,

Op 22-06-2021 om 01:25 schreef Johnny A. Solbu:

...

Then I also noticed an inconsistency in how "..." is 'translated'

The reason is quite simple: muscle memory. For some reason I find it easier to just type «AltGr+.» which produces that.

I have done a Search & Replace on all instances.

Thanks. However, there are still six occurrences where the three dots are preceded by a space, whereas most occurrences are not.

...

-Q <reg.uttrykk> --quotestr=<reg.uttrykk>Regulært uttrykk for å matche sitering

It would look better if "reg.uttrykk" were abbreviated to "reg.utt."; what it is an abbreviation of is shown right after it: "Regulært uttrykk...".

The shortest we can do in norwegian is actually «Reg. uttrykk». This really is the shortest we can do it.

Then maybe add two space at the end of msgstr "--quotestr=<reg.uttrykk>", so that the explanatory text doesn't get glued to it?

Besides, the english source msgid does not abreviate this it in its explanation of the string.

Exactly. That's why it's fine to abbreviate it rather aggressively in the two columns before it -- the full phrase follows immediately after.

...

M-P Vis usynlige tegn (mellomrom, tab, linjeskift osv.) skru på/av

But M-P makes only spaces and tabs visible, not newlines or any other whitespace.

Not corrected yet.

...

Also in the ^G help text, the phrase that starts with "De to nederste linjene viser..." occurs twice. The first occurrence of that string is misplaced, as are the two subsequent \n.

According to the TP archive, these two was done by the previous translator. I'll fix it.

You forgot to remove the two \n after "viktige meldinger." After "viktige meldinger." should just be one or two spaces, depending on your spacing style (see the msgid).

...

msgid " [Case Sensitive]" msgstr " [skill mellom små og store bokstaver]"

This is the same issue as with regexp. This Not-so-short translation really is the shortest we can do it, in Norwegian. We really do not have any other way to convey that something depends on the size of letters.

It's not really necessary to fully convey the meaning of "Case sensitive". This phrase is one of three things that can get affixed to the Search prompt: it's either [Backwards], or [Regexp], or [Case Sensitive]. It's enough when the translation is just specific enough so that the user cannot confuse it with [Bakover] and [Regulært uttrykk].

Looking around more in nb.po, I now see that the translation for "Case Sens" is far too long:

msgid "Case Sens" msgstr "Følsomt for store/små bokstavar"

On an 80-column terminal, the user gets to see just this:

^G Hjelp M-C Følsomt for M-B Bakover ^C Avbryt M-R Reg.exp. ^R Erstatt

I know this is impossible to expresss in just eleven letters -- even the English needs to use a creative abbreviation -- but these are the limits of the nano interface.

Also notice that "Reg.exp" is not translated.

msgid "Go To Dir" msgstr "Gå til katalog"

This one I would suggest to shorten to: "Til katalog", in order to fit.

msgid "Prev Line" msgstr "Forrige side"

This looks wrong.

msgid "Comment Lines" msgstr "Kommentarlinjer"

The "Comment" in this msgid is a verb. In the translation you may want to forget the "Lines" and just say something like "Kommentarer". These short tags are just hints -- fuller explanations are in the ^G help.

#. TRANSLATORS: Remember: these are nouns, NOT verbs. msgid "cut" msgstr "Klipp ut"

msgid "paste" msgstr "Lim inn"

msgid "indent" msgstr "Innrykk"

msgid "unindent" msgstr "Angre «innrykk»"

msgid "comment" msgstr "Kommentar"

msgid "uncomment" msgstr "Avkommenter"

These should all start with a lowercase letter, and, as noted in the comment, these are all nouns, of an action that was performed -- they are not commands. So the first of these should probably be something like "utklipping". Likewise for the others. See the few msgstrs that precede them in the PO file.

Benno