I'v got a little question about the translation of an entity. I know that in a
lot of case I shouldn't translate it an simply let it (eg : &krusader;). But
if it has no meaning (in french for example) what should I do ?

An example can be :

I was forget to mention it, sorry.
Don't translate &foo; entities in the po files. Once all po files are
translated, i will send you a index.docbook file where you can
translate all entities into French.
When all po files are translated, about 99% of the handbook is
translated (except the entities of index.docbook).

I have used several entities, eg. if a url is used several times in
the handbook, so i need only to modify one entity in index.docbook to
modify the complete handbook,
somehow the po tools doen't support translating entities (or i don't
know yet how to do this).

thanks and bye,

The most easy is to edit this file with Krusaders "F4" Edit function
(opens a Editor), this will give you syntax higlighting.

Only translate the next entities:
<!ENTITY Backspace   "<keycap>Backspace</keycap>">
and the next sections:
<!-- internet links, Krusader -->
<!-- internet links, others -->
<!-- documentation links -->
<!-- markup ENTITIES -->
I guess the next enties don't need to be translated
<!-- application ENTITIES -->
<!-- (TM) Trademark ENTITIES -->
<!-- (R) Registered ENTITIES -->
<!-- (C) Copyright ENTITIES -->
<!-- useraction ENTITIES --> (the useraction parameter syntax will
stay in English i think)

When translating entities, only tanslate the latter part:
e.g
<!ENTITY Backspace   "<keycap>TRANSLATION OF BACKSPACE</keycap>">
<!ENTITY kruwebsite-url '<ulink
url="http://www.krusader.org">TRANSLATION OF Krusader
website</ulink>'>

Don't edit the first (or middle part) of the entity, the first part is
the &foo; entity that you see in your pot file.

Note: please don't modify anything else, all other stuff that needs to
be translated is in index.docbook.pot

p.s.
If somebody know how entities can be better managed for i18n, you can
always e-mail me, i know it's not a good solution.
It would be nice to have a po file that handles this krusader specific
entities, but i don't know that this is possible.
In this case a translator needs only to translate po files.
I could remove all Krusader specific entities in the future and use
several identical urls around the docbook files, though i don't like
the idea. It also means more translating work. Now i define one
English entity and use it several times in the documenation with
calling &foo;.

thanks and bye,