3:11 a.m.
On 2010/10/24 David Prévot wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 17/10/2010 16:08, David Prévot a écrit :
[...]
> Using these conventions makes the manual pages really easier to read and
> search for information [...] that's why I initiate the branches/manpage
> branch, not to break current translations and so on.
I think It's done.
> Once this will be OK, there will be again some work to manually unfuzzy
> translations, since most of this change may be unfuzzy before asking for
> update.
I'll proceed soon, unless someone objects to the proposed changes, of
course. If someone want to join the unfuzzy effort, the four already up
to date translations (Spanish, French, Japanese and Polish) have two
hundred string to unfuzzy (for each language ;-). Changes are trivial,
but there are lots of them.
Hi David,
[Reply sent to po4a-devel instead of po4a-commits. Original thread at
http://lists.alioth.debian.org/pipermail/po4a-commits/2010-October/002896...
]
I do not know how you want to proceed to merge your branch into trunk,
you can merge it now if you want, or when it is finished, it is up to
you.
You will have to be careful to not unfuzzy SVN r2296, I suggest you to
undo this change in your branch and apply it instead on the trunk
(either before or after the merge, as you want).
Thanks for your work.
Denis
9:59 a.m.
New subject: [Po4a-devel] ] Following man-pages conventions (Was: r2287 - /branches/manpage/)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Le 24/10/2010 04:11, Denis Barbier a écrit :
I do not know how you want to proceed to merge your branch into
trunk,
you can merge it now if you want, or when it is finished, it is up to
you.
I thought it would be better to unfuzzy translation before merging (I
may add some changes to the original documentation during the manual
unfuzzing).
You will have to be careful to not unfuzzy SVN r2296, I suggest you
to
undo this change in your branch and apply it instead on the trunk
(either before or after the merge, as you want).
I think it is OK (understand there is no way I can unmark fuzzy this
paragraph shorten by its half), but thanks for pointing it anyway, I'll
double check (or simply temporally hold it as you advised). I also
intend to s/. /. / (some double space by mistake) in the source code
because they might be showed in the resulting manpage when the source is
a POD file, but since this could be automatically unfuzzy, I'll do it
after the manual unfuzzy.
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkzESdAACgkQ18/WetbTC/p5aACff4lCVfkmwRdeonHkRD+nhdk4
/2UAnAqvbPjUw36AUM6Jz9qN4u2NfR/a
=1OkB
-----END PGP SIGNATURE-----
8:40 p.m.
New subject: [Po4a-devel] ] Following man-pages conventions (Was: r2287 - /branches/manpage/)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 24/10/2010 10:59, David Prévot a écrit :
Le 24/10/2010 04:11, Denis Barbier a écrit :
I thought it would be better to unfuzzy translation before merging
(I
may add some changes to the original documentation during the manual
unfuzzing).
Done: branches/manpage reintegrated trunk.
> You will have to be careful to not unfuzzy SVN r2296, I suggest
you to
> undo this change in your branch and apply it instead on the trunk
> (either before or after the merge, as you want).
I followed your advice and merge it back to the trunk after the merge. I
may also fix some more typos spotted in the process, but I intend to
perform automatic unfuzzy, so it won't be as much disruptive.
s/containg/containing/
s/ie/i\.e\./
s/Po4a/po4a/
s/\. /\. /
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkzGMYkACgkQ18/WetbTC/q8mgCdFllXmrEXv+CMdFz6JvQ3yZkY
Up8An3/XLIHlCCjPc2yWEF7GiyfhDe2t
=XMRG
-----END PGP SIGNATURE-----
5174
days inactive
5176
days old
2 comments
2 participants
participants (2)
-
David Prévot -
Denis Barbier