X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/04283202372ad7aec8dc038ffb5d98f07aacd871..bc4ef28f3ebc396096b7eccad04eea6febac8d38:/doc/translation/discussion.mdwn?ds=sidebyside

diff --git a/doc/translation/discussion.mdwn b/doc/translation/discussion.mdwn
index 32cc3f5e9..35e8fd054 100644
--- a/doc/translation/discussion.mdwn
+++ b/doc/translation/discussion.mdwn
@@ -17,15 +17,8 @@ updating my PO file? Should I send it to you for every ikiwiki issue?
 Maybe you should give write access to ikiwiki repository for translators
 of PO files?
 
-  > I recently set up a git repository mirroring the main svn repository (see
-  > [[download]]) and one idea is that perhaps translators can use that for a
-  > distributed revision control system that I can merge back from into svn.
-  > I can set up accounts for svn, but as it's on my own personal server and
-  > not a sourceforge/alioth like thing, it's a bit of a pain and maintenance
-  > burden for me.
-
-  >> OK, I've picked up Subversion for your ikiwiki, so I can get into
-  >> Git now ;)
+  > We use git now, so you can clone my repo, commit to your clone, and
+  > use git to mail me patches. --[[Joey]] 
 
 3. What is the best way to update my PO file when you do some changes in
 `ikiwiki.pot` file? Should I translate my PO file from scratch or
@@ -43,16 +36,16 @@ can I do diff for old and new `ikiwiki.pot` file and update only differences?
   >>>> OK, I hope I handle it :)
 
 4. What about "gettexting" button titles and link names? Do you really
-think that there should be hardcoded in ikiwiki templates? --Pawel
+think that there should be hardcoded in ikiwiki templates? --[[Paweł|ptecza]]
 
   > I don't know, really. Recai's approach seems to show promise.
 
   >> BTW, why does ikiwiki number my questions wrongly (1., 1., 1., 1.,
-  >> instead of 1., 2., 3., 4.)? Where have I made a Markdown mistake? --Pawel
+  >> instead of 1., 2., 3., 4.)? Where have I made a Markdown mistake? --[[Paweł|ptecza]]
 
   >>> My indentation mistake, I think. --[[Joey]]
 
-  >>>> Now it's perfect :) Thank you very much! --Pawel
+  >>>> Now it's perfect :) Thank you very much! --[[Paweł|ptecza]]
 
 ----
 
@@ -71,4 +64,27 @@ a message is. Then I have to check the sources again...
 So I have a request to Joey and the rest of ikiwiki coders:
 please write more verbose gettext messages and don't fear using
 subject there. It will be huge help for me and other ikiwiki
-translators. Thank you! :) --Pawel
+translators. Thank you! :) --[[Paweł|ptecza]]
+
+> Well, those messages are mostly laconic because they're output by
+> ikiwiki running in unix program mode and other tight situations, and 
+> it should be clear from context when you see the expanded message what
+> the various bits are. 
+> 
+> For example, "update of foowiki's MooBar by joey" seems to say enough to
+> be clear (and fit in mutt's subject line display), while the corresponding
+> "actualizado el wiki foowiki y la página MooBar por el usuario joey" feels
+> a bit verbose. (And should it say "updated foowiki *and* the MooBar page"
+> like that? My Spanish sucks though..) In my crappy Spanish I might instead
+> say something like "actualizado MooBar de foowiki por joey". Or maybe
+> "actualizado página Moobar por joey"?
+
+>> But you know that "update of %s's %s by %s" string can be "update of
+>> foowiki's MooBar by joey", but I can only guess it :)
+
+> Anyway, to get back to your point, it's true that translators often
+> need additonal context about things like what variables expand to, and
+> size limits. This is generally done by adding comments in the pot file,
+> and I've turned that on, and added a few. --[[Joey]]
+
+>> Thank you very much! It also will be a big help for me. --[[Paweł|ptecza]]