X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/82ce2c25be0a42fba744ebec80dd17d31595f720..efac37267afa8ea194117d60a69d6a5dd253c962:/doc/translation/discussion.mdwn?ds=inline

diff --git a/doc/translation/discussion.mdwn b/doc/translation/discussion.mdwn
index 0383d49c2..ed034910f 100644
--- a/doc/translation/discussion.mdwn
+++ b/doc/translation/discussion.mdwn
@@ -1,3 +1,5 @@
+# A few questions about translating PO file
+
 I have a few questions about translating PO file:
 
 1. Assume I copied `ikiwiki.pot` file to `pl.po` file and translated it
@@ -38,6 +40,8 @@ can I do diff for old and new `ikiwiki.pot` file and update only differences?
 
   >>> I'm not a translator, so I don't really know..
 
+  >>>> 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
 
@@ -47,3 +51,47 @@ think that there should be hardcoded in ikiwiki templates? --Pawel
   >> instead of 1., 2., 3., 4.)? Where have I made a Markdown mistake? --Pawel
 
   >>> My indentation mistake, I think. --[[Joey]]
+
+  >>>> Now it's perfect :) Thank you very much! --Pawel
+
+----
+
+# Less laconic gettext messages
+
+I'm just translating `ikiwiki.pot` file to Polish and I have
+problems with some gettext messages, because unfortunately
+there are very laconic, for example "update of %s's %s by %s".
+
+Sometimes I don't understand background well, because I don't use
+all ikiwiki plugins and I have to check ikiwiki source code.
+Besides in Polish language we have conjugation of a verb and
+I can't do it correctly if I don't know what subject of
+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
+
+> 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. --Pawel
\ No newline at end of file