>>>> 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]]
----
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
> 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]]
\ No newline at end of file