Hello Osamu, On Tue, Jul 01, 2014 at 10:20:23PM +0900, Osamu Aoki wrote: > > > Hmmmm... I wrote these in many years and may be lost track of the style > > > consistency. Unless all fixes are in one patch for the whole document > > > and complete, I would rather pass this colon fixes to avoid overloading > > > translatiors. > > > > If you agree with the fix in principle, I can look through the > > document, apply the fix and unfuzzy all translations with latin or > > cyrrilc script (sorry, I'm unfamiliar with any other script including > > their punctuation rules). I would wait of course until the current > > updates arrived to avoid confusing translators. > > > > Would you be ok with this workflow? > > Yes, as long as the whole document is fixed at once. > I can do unfuzzy for Japanese. (No new Chinese build) > (Unfuzzying is the big headach for me.) > > I am afraid of collision with the new translation updates. > > So may I ask you to send me a patch from your chosen commit in the git. > I will do robust merging using gettext.
I'm not entirely sure what my patch should contain. Only patching the original (i.e. the English text)? Or should I provide you with patches for the latin/cyrillic based languages as well? I can provide you with patches so that for the latin/cyrillic based languges no new fuzzy/untranslated strings appear. (I've done this already several times for various packages). Which time would be best for you? I suggest after the release of this version of maint-guide, i.e. at/before the start of the next version. > > > > -"literal> for libraries, <literal>mail</literal> for email readers and > > > > " > > > > +"literal> for libraries, <literal>mail</literal> for e-mail readers > > > > and " > > > > > > "email" without - is accepted in the US style. Changing one out of > > > many is also bad. > > > > It simply looks strange to me. > > That is not strong argument after I explained my choice is a concious > one. Since you insist, I made further study on subject. google word > hit counts are about the same. Then I found Wikipedia article on "email" > with the primary spelling being "email" :-) Its article starts with spelling. > http://en.wikipedia.org/wiki/Email#Spelling > Electronic mail has several English spelling options that occasionally > are the cause of vehement disagreement. > (very interesting summary, please read) > > So I am absolutely going to stay with the spelling "email". This is > technical document following IETF and Achaddemic practice is the right > one. Oh, sorry, I did not mean to insist, I just expressed my personal opinion. But many thanks for your research (I did not intend to cause you so much work, sorry). > > > > The following sentence is unclear to me. I did my best to translate it, > > > > but you should consider rewording it: > .... > > Could you phrase this one more clearly? I really have trouble parsing > > it. > > How about: > > The actual triplet path is dynamically set into the > <literal>$(DEB_HOST_MULTIARCH)</literal> variable using the > <citerefentry> > <refentrytitle>dpkg-architecture</refentrytitle><manvolnum>1</manvolnum></citerefentry> > command for each binary package build. Yes, this is perfectly understandable to me. > > Typo? I'm not sure about this one: > > -"<command>pdebuild</command> (used by <command>gbp buildpackge</command>)" > > +"<command>pdebuild</command> (used by <command>gbp buildpackage</command>)" Thanks again Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
