From 82ce2c25be0a42fba744ebec80dd17d31595f720 Mon Sep 17 00:00:00 2001 From: joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> Date: Sun, 31 Dec 2006 20:54:40 +0000 Subject: [PATCH] response --- doc/translation/discussion.mdwn | 44 ++++++++++++++++++--------------- 1 file changed, 24 insertions(+), 20 deletions(-) diff --git a/doc/translation/discussion.mdwn b/doc/translation/discussion.mdwn index cf9ffdf74..0383d49c2 100644 --- a/doc/translation/discussion.mdwn +++ b/doc/translation/discussion.mdwn @@ -5,41 +5,45 @@ from English to Polish. How can I check that my `pl.po` file works good? I have some experience with building Debian packages, but I don't know too much about working with PO files in Debian packages. -> Try putting it into the po/ directory and running make and make install -> in there, that should create the .mo and install it somewhere -> appropriate. ikiwiki should display translated messages when building the -> wiki (with -v). + > Try putting it into the po/ directory and running make and make install + > in there, that should create the .mo and install it somewhere + > appropriate. ikiwiki should display translated messages when building the + > wiki (with -v). 2. I'll send you my translation when I finish it, of course. But what about 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. + > 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 ;) + >> OK, I've picked up Subversion for your ikiwiki, so I can get into + >> Git now ;) 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 can I do diff for old and new `ikiwiki.pot` file and update only differences? -> There are standard tools for working with po files, and the po file -> should be updated as part of the wiki build process so that any fuzzy -> strings are so marked. + > There are standard tools for working with po files, and the po file + > should be updated as part of the wiki build process so that any fuzzy + > strings are so marked. ->> Could you please point me any good references or write a quick start ->> for translators? I think it can be very useful for me and other people. + >> Could you please point me any good references or write a quick start + >> for translators? I think it can be very useful for me and other people. + + >>> I'm not a translator, so I don't really know.. 4. What about "gettexting" button titles and link names? Do you really think that there should be hardcoded in ikiwiki templates? --Pawel -> I don't know, really. Recai's approach seems to show promise. + > 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 ->> 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 + >>> My indentation mistake, I think. --[[Joey]] -- 2.39.5