0> In article <008501be0bcf$d11e43f0$10c809c0@corba.netaway>,
0> Sebastien wrote:
Sebastien> My first thought will be the following:
Sebastien> ...
Sebastien> <method id=3D"fact">
Sebastien>
Sebastien> <description lang=3D"english">The factorial =
method</description>
Sebastien> <description lang=3D"french">La m=E9thode =
factorielle</description>
Sebastien> <description lang=3D"spanish">La operac=EDon =
factorial</description>
Sebastien>
Sebastien> <param id=3D"Nbr" mode=3D"in" type=3D"int">
Sebastien> <description lang=3D"english">The number to pass =
in</description>
Sebastien> <description lang=3D"french">Le nombre =E0 =
passer</description>
Sebastien> <description lang=3D"spanish">El n=FAmero a =
calcular</description>
Sebastien> </param>
Sebastien>
Sebastien> </method>
Sebastien> ...
That's one way of doing it, though it seems to be more common to
have a separate document for each language. The latter approach
makes it easier to add new translations with minimum disturbance
to existing work (in particular, it reduces the likelihood of
check-out conflicts in a source control system), and it means that
only the required language mappings need be copied during software
installation, reducing disk space requirements for end-users.
You might want to use the XML-defined xml:lang attribute for your
language labels, BTW, with the usual Internet language codes:
xml:lang=3D"en-GB" or xml:lang=3D"fr-CA".=
--