Re: proofreading the installation-guide
Holger Wansing wrote:
> Justin B Rye <firstname.lastname@example.org> wrote:
>>>> So all cases of &releasename-cap; in the English text are mistakes.
>>>> Really if it's only for use in German we should have called it
>>> No, it's not just for German!
>>> It gives _all_ translators the possibility, to spell the releasename as
>>> they want in their language.
>>> I just used German and how it's used in German, to explain the principle.
>>> Not much translators use that possibility though.
>> Such as? There *aren't* any other languages that have mandatory
>> initial capitalisation on nouns (and even German allows exceptions for
>> "brandnames" like "das iPhone" or "xkcd"). There's not much else that
>> you could automate, so I'd be interested to know who else finds it
> A quick grep shows, that releasename-cap is used in:
> So guys, you are all wrong?
If they're just using it to capitalise a brandname that we've decided
is canonically uncapitalisable then it's just a question of whether
they're doing it wrong or whether the decision was wrong for English
in the first place.
But if you take a proper look at the results of that grep, you'll see
that every single case is a reflection of the same problem: there are
a couple of files where the English text has randomly switched to
using &releasename-cap;, and those hits are just the places where the
translators haven't changed it.
So once my proofreading sweep has finished* and all the translations
catch up, there should be no mentions of &releasename-cap; except in
places where it might as well be called &Veroeffentlichungsname;.
* assuming it ever gets started...
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package