Hello Yves, all, there is a reason that you don't have such facilities in many text oriented formats (also HTML, DocBook, DITA): versions in different languages are often created via translation with many participants: creators of original content, localization engineers preparing often a lot of documents (or speaking more generally "pieces of content") for localization, translators / localizers doing the actual translation etc., quality assurance people etc. And in this chain of content processing of course there are also cycles possible, e.g. from the QA people to the translators ...
The participants in this chain would have a hard life if they would have to know every format in detail and would have to edit the formats directly. For this reason, normally content to be localized is extracted from various source formats, and at the end of the workflow put into the original again. A standard to manage that workflow is XLIFF, see the example in sec. 2 at http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#SectionStructure . Using XLIFF and setting up such a localization chain might be an overkill for your problem, but maybe a sustainable solution which you then can easily use for additional formats, not only Atom. Best, Felix 2010/9/2 Yves Dorfsman <[email protected]> > > > Hi, > > Is there a proper way to specify a title and an summary for an entry in two > different language? > > I have tried to specify two title and summary with different xml:lang="xx" > in the same entry but it does not validate, and aggregators get confused. > > I have tried different combination of html and xthml with <div lan="xx">, > but again, when I do manage to make those validate, the aggregators just > print both on the same line. > > Finally I created two entries, both with the same ID, update and link, but > with a different lang tag <entry xml:lang="xx">, and different title and > summary. This seems to be the cleanest, but the aggregators see those as two > separate entries... > > Thanks. > > -- > Yves. > http://www.SollerS.ca/ > > xmpp:[email protected]<xmpp%[email protected]> > > >
