summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-07-19 15:01:00 +0200
committerJoey Hess <joey@gnu.kitenet.net>2009-07-19 15:01:00 +0200
commit7f134d77d326df0b3d4762c4bd5f3f402794be0a (patch)
tree891ab33e5072b7affb68a68a2441457a6d18f581
parentd00211524b64ac269c1ac2fd7f1a8fde1ffbbd8e (diff)
update
-rw-r--r--doc/translation.mdwn6
-rw-r--r--doc/translation/discussion.mdwn13
2 files changed, 6 insertions, 13 deletions
diff --git a/doc/translation.mdwn b/doc/translation.mdwn
index 005d9c889..22801d997 100644
--- a/doc/translation.mdwn
+++ b/doc/translation.mdwn
@@ -22,7 +22,7 @@ essentially three pieces needed for a complete translation:
* The names and values of parameters, both to the program, in the setup
file, and in preprocessor directives.
-1. The [[basewiki]] itself needs to be translated. The
+1. The [[basewiki]] needs to be translated. The
[[plugins/contrib/po]] ikiwiki plugin will allow translating
wikis using po files and can be used for this.
@@ -33,8 +33,8 @@ essentially three pieces needed for a complete translation:
ones you'll want to translate are in the `po/underlays/basewiki` directory,
which is really not very large, just a few thousand words.
After that is done, you can tackle those under
- `po/underlays/directives`, which are a much larger tens of
- thousands of words.
+ `po/underlays/directives`, which are a much larger (tens of
+ thousands of words).
1. The templates also need to be translated. Some work has been done on an
infrastructure for maintaining translated templates, as documented in
diff --git a/doc/translation/discussion.mdwn b/doc/translation/discussion.mdwn
index 26097b555..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
@@ -94,4 +87,4 @@ translators. Thank you! :) --[[Paweł|ptecza]]
> 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
+>> Thank you very much! It also will be a big help for me. --[[Paweł|ptecza]]