* 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.
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
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
> 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]]