Cart
[Home] [By Thread] [By Date] [Recent Entries]
Sebastien> Sebastien Sahuc <URL:mailto:ssahuc@n...> 0> In article <008501be0bcf$d11e43f0$10c809c0@c...>, 0> Sebastien wrote: Sebastien> My first thought will be the following: Sebastien> ... Sebastien> <method id="fact"> Sebastien> Sebastien> <description lang="english">The factorial method</description> Sebastien> <description lang="french">La méthode factorielle</description> Sebastien> <description lang="spanish">La operacíon factorial</description> Sebastien> Sebastien> <param id="Nbr" mode="in" type="int"> Sebastien> <description lang="english">The number to pass in</description> Sebastien> <description lang="french">Le nombre à passer</description> Sebastien> <description lang="spanish">El número 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="en-GB" or xml:lang="fr-CA". -- xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
