Sebastien Koechlin <seb.joe@...> wrote:
>I was able to compile joe wednesday, but today I have errors again, automake
>and autoconf are reporting errors.
I've been working on it...
>./INSTALL is not up to date, there is nothing about automake and autoconf,
>minimal version to use and in which order they should be run.
It's in INSTALL.cvs. You need to type ./autojoe to rerun all the auto junk.
>Anyway, here is a first french translation, started on joe.pot 1.2 and
>patched to upgrade to 1.5.
>There are some strings not translated
I think this is OK.
>-because I don't really understand what does it means and when joe print it:
> is joe keymap really a map for keyboard? Is it about keys or
> characters, or glyphs?
It's the name of a keymap in the joerc file (like ":main")- a table of key
sequence to macro bindings.
>I don't understand what is a buffer,
A file loaded into JOE.
If you jump into a menu and click on a directory, then if this option is
set, it leaves the cursor in the menu, otherwise it puts it back in the
When you hit ^KF, the prompt suggests reusing the previously entered search
string when this is set.
Maybe this is -csmode? It ^KF just repeats the search instead of prompting
for a new string.
The rows and columns of file name completion menus are swapped.
I was thinking about this. I will try to add comments in the source code
(since there is a reference to the source code in the comment above the
msgid) explaining the meaning of short strings.
>-I keep If/Then/Else/Endif/Repeat in macro in english, because I think it
>would break a lot of things, and I don't want joe to understand commands
>depending of configured locale.
>-I did not translate option menu (^T) for the moment. French take more space
>and I have to find really small text to fit in thoses littles spaces,
>understandable both by old (having english menu for years) and new users.
You can make them longer, but then fewer will fit on the screen (the number
of columns in ^T gets reduced).
>-Finding options are not translated because I have problems with characters
>list. When the same value is used more than once, they are present
>only one time, for example:
> #: cmd.c:216 usearch.c:557
> msgid "iI"
I will see if there is any way to force xgettext to leave these as separate
strings. One stupid way is to put a prefix string in the msgid string, but
I'd prefer not to do that.
>iI is for "Edit anyway" in cmd and "Ignore" in usearch.
>Should I duplicate thoses lines, one for cmd and one for usearch?
Let me think about it, update CVS and contact you again.
>How a po file is updated to match next update/new strings?
There is a program called msgmerge which does this. It keeps the existing
translations, adds msgids for new strings and comments out obsolete strings.