Hello,
Justin B Rye, on Thu 04 Feb 2016 09:48:05 +, wrote:
> It's looking as though the only way this is going to be doable is if
> I split it up into multiple runs with different methodologies:
> 1) things like converting → and dhcp → DHCP
> which ought to be introduced across the wh
Christian PERRIER wrote:
> Quoting Samuel Thibault (sthiba...@debian.org):
> There is ("msgattrib --clear-fuzzy") but this will un fuzzy also what
> was fuzzy before, which is not intended.
>
> The real safe way is the first method:
>> - fix the english text
>> - fix the english version in the cor
Quoting Samuel Thibault (sthiba...@debian.org):
> I.e. changing the english text, which will make the translations fuzzy
> for no reason. In that case, you can either:
>
> - fix the english text
> - fix the english version in the corresponding .po files *exactly* the
> same way, so that po updat
Hello,
Getting back to this discussion, sorry it took so long for finding out
the time to do it.
Justin B Rye, on Sat 12 Sep 2015 15:23:44 +0100, wrote:
> Assuming I can get write access,
That shouldn't be a problem, just tell us your alioth id.
(I'm not an admin there, so somebody else will hav
Baptiste Jammet wrote:
> Dixit Justin B Rye:
>> Assuming I can get write access, how do I minimise the pain?
[...]
>> But while I know a few basic svn commands (which is more than I'll ever
>> understand of git), it's not clear to me whether doing (a), (b), (c),
>> and (d) as successive commits wou
Hi,
Dixit Justin B Rye, le 12/09/2015 :
>Assuming I can get write access, how do I minimise the pain? I could
>split the changes into:
>
> a) fixes for the English that shouldn't affect translations (e.g.
>correcting Germanic uses of "respectively", objectless "allow",
>etc.)
> b) fixes t
Baptiste Jammet wrote:
>> At this stage what I'd *like* to be able to do is submit half a dozen
>> different patches for different types of recurring problem - one to
>> tidy up the s and s, one to fix up the outbreaks of
>> un-English grammar, one to correct the capitalisation of titles, and
>> so
eed to discover the very subtle variations. So I don't
want to wait the end of the release cycle !
Your plan A is OK for me.
Moreover, there were no objections on your wordings since several weeks,
so (in my opinion) please go ahead.
Thanks for proofreading the installation-guide.
Baptiste
pgpfMrDMB9wMu.pgp
Description: OpenPGP digital signature
Justin B Rye wrote:
> First, the deep-rooted termininological issues that I'd prefer to have
> sane answers for before I start fiddling with details:
>
> * why is there so little mention of BD media? [...]
> * D-I seems to have standardised on the term "MD devices" [...]
> * is there any hope
Samuel Thibault wrote:
> Justin B Rye, le Fri 07 Aug 2015 15:52:00 +0100, a écrit :
>> It's not immediately obvious why we're going to the trouble of
>> distinguishing from (along with ,
>> , , and who knows what else). I'm sure it's all
>> lovely and semantic, but all we actually want is for th
Justin B Rye, le Fri 07 Aug 2015 15:52:00 +0100, a écrit :
> It's not immediately obvious why we're going to the trouble of
> distinguishing from (along with ,
> , , and who knows what else). I'm sure it's all
> lovely and semantic, but all we actually want is for them to be
> flagged as verbati
Holger Wansing wrote:
> Justin B Rye 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
&Veroeffentlichungsname;!
>>>
>>> No, it's not just for German!
>>> It gives _all_ translators the possibil
Samuel Thibault wrote:
> On to spending some time on answering this...
Well, you may have noticed I'm rather taking the long view on actually
getting started on stage one.
> Justin B Rye:
>> First, the deep-rooted termininological issues that I'd prefer to have
>> sane answers for before I start
Hi,
Justin B Rye 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
> >> &Veroeffentlichungsname;!
> >
> > No, it's not just for German!
> > It gives _all_ translators the possibility, to spell the r
Hello,
On to spending some time on answering this...
Justin B Rye, le Sun 26 Jul 2015 13:15:18 +0100, a écrit :
> A month ago in #789604, Justin B Rye wrote:
> > Hmm, well, I've never proofread the installation-guide as a whole. I
> > ought to get round to doing that some time.
>
> I'm trying t
Holger Wansing wrote:
> Justin B Rye wrote:
>> Holger Wansing wrote:
>>> No, not _all_ instances of &releasename; have to be capitalised in German,
>>> for example in URLs they will have to stay lowercase.
>>> But I can use &releasename; or &releasename-cap; in my translation,
>>> where &releasena
Justin B Rye, le Tue 28 Jul 2015 21:06:03 +0100, a écrit :
> Holger Wansing wrote:
> > Justin B Rye wrote:
> >> An interesting idea, but one that seems unlikely to work, especially
> >> given the way it's used in the text. For instance, there's a page
> >> "welcome/what-is-debian-linux.xml", whic
Hi,
Justin B Rye wrote:
> Holger Wansing wrote:
> > No, not _all_ instances of &releasename; have to be capitalised in German,
> > for example in URLs they will have to stay lowercase.
> > But I can use &releasename; or &releasename-cap; in my translation,
> > where &releasename; is used in Engli
Holger Wansing wrote:
> No, not _all_ instances of &releasename; have to be capitalised in German,
> for example in URLs they will have to stay lowercase.
> But I can use &releasename; or &releasename-cap; in my translation,
> where &releasename; is used in English.
So all cases of &releasename-ca
On Tue, Jul 28, 2015 at 09:06:03PM +0100, Justin B Rye wrote:
> Holger Wansing wrote:
> > Justin B Rye wrote:
> >> An interesting idea, but one that seems unlikely to work, especially
> >> given the way it's used in the text. For instance, there's a page
> >> "welcome/what-is-debian-linux.xml", w
Hi,
Justin B Rye wrote:
> Holger Wansing wrote:
> > Justin B Rye wrote:
> >> The "&debian-gnu;" entity is effectively just shorthand for "Debian
> >> GNU/&arch-kernel;" - confusing but handy.
>
> Wait, does it expand to Debian or &debian;?
&debian-gnu; -> &debian; GNU/&arch-kernel; -> Debian G
Holger Wansing wrote:
> Justin B Rye wrote:
>> An interesting idea, but one that seems unlikely to work, especially
>> given the way it's used in the text. For instance, there's a page
>> "welcome/what-is-debian-linux.xml", which is full of sentences like
>> "&debian; was the first Linux distribu
Hi,
Justin B Rye wrote:
> Hendrik Boom wrote:
> > Justin B Rye wrote:
> >> * &entity questions - when am I meant to say "Debian" and when is it
> >>"&debian;"? This like many of these entities seems to have no
> >>obvious function other than to make the source harder to
> >>interpre
On Sun, Jul 26, 2015 at 02:37:45PM +0100, Justin B Rye wrote:
> Hendrik Boom wrote:
> > Justin B Rye wrote:
> >> * &entity questions - when am I meant to say "Debian" and when is it
> >>"&debian;"? This like many of these entities seems to have no
> >>obvious function other than to make t
Hendrik Boom wrote:
> Justin B Rye wrote:
>> * &entity questions - when am I meant to say "Debian" and when is it
>> "&debian;"? This like many of these entities seems to have no
>> obvious function other than to make the source harder to
>> interpret...
>> * The &d-i; entity expa
On Sun, Jul 26, 2015 at 01:15:18PM +0100, Justin B Rye wrote:
> * &entity questions - when am I meant to say "Debian" and when is it
> "&debian;"? This like many of these entities seems to have no
> obvious function other than to make the source harder to
> interpret...
> * Th
A month ago in #789604, Justin B Rye wrote:
> Hmm, well, I've never proofread the installation-guide as a whole. I
> ought to get round to doing that some time.
I'm trying to work out where I'd start with this. I can see things
that need fixing, but they fall into several different categories an
27 matches
Mail list logo
