IETF Logo Mail Archive

Re: syntax for bilingual page

Felix Sasaki <felix.sasaki@fh-potsdam.de> Wed, 08 September 2010 07:02 UTC

Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55D603A67E5 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 8 Sep 2010 00:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.177
X-Spam-Level: *
X-Spam-Status: No, score=1.177 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxvsPwYJlQIg for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 8 Sep 2010 00:02:37 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id F32F83A657C for <atompub-archive@ietf.org>; Wed, 8 Sep 2010 00:02:36 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o886w6B6022833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Sep 2010 23:58:06 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o886w697022832; Tue, 7 Sep 2010 23:58:06 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o886w4lZ022825 for <atom-syntax@imc.org>; Tue, 7 Sep 2010 23:58:05 -0700 (MST) (envelope-from felix.sasaki@googlemail.com)
Received: by wwf26 with SMTP id 26so7383389wwf.22 for <atom-syntax@imc.org>; Tue, 07 Sep 2010 23:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=II/MD8pwqBcjgiqtBkkQ9utKaDa9KhpkrXdIJtvJ9Og=; b=FvY1Ny7Ay1YfshdHMQwruFthFy89jVq2PoTi0Q+fQczpxL89JqEMDdCFRG0f5PM+cC dPMwvtXN7FT3Iy3uHKVO6HZLiL/JmAofl8GDY1tVRv3Rb8+Fw6v5ezhm8HMJH/+f6lLA 3j0tqZnYqavHTRVaLgVZUi04nl1UiIIpU7KHs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=sP3BJLyXXQPEbL+YVvPSr48AsK7obfiZ3gCE3Xrm5jTq3/44lU4YHhHPNzLoz23p2K fhzrJc+JdZvNLFq1wA1zqeu0PIQH85Lzz8m4b74aY99LMqXTFeJuh3YnZiAhKzE5nJnF hJKQW2nJPEF9QGGBBHSyiKwfKWG0dWJqN9FHQ=
MIME-Version: 1.0
Received: by 10.227.155.3 with SMTP id q3mr71399wbw.130.1283929073028; Tue, 07 Sep 2010 23:57:53 -0700 (PDT)
Received: by 10.227.143.77 with HTTP; Tue, 7 Sep 2010 23:57:52 -0700 (PDT)
In-Reply-To: <4C7F432A.3070506@zioup.com>
References: <4C7F432A.3070506@zioup.com>
Date: Wed, 8 Sep 2010 08:57:52 +0200
X-Google-Sender-Auth: zxP8Xz2gwTi47UgOFL4ncOpswHg
Message-ID: <AANLkTimSHbKv5aU7jESuR0pcezTVCrKA6dLjLcWVTrwM@mail.gmail.com>
Subject: Re: syntax for bilingual page
From: Felix Sasaki <felix.sasaki@fh-potsdam.de>
To: Yves Dorfsman <yves@zioup.com>
Cc: atom-syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=0016367fab6550914b048fba0857
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

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 <yves@zioup.com>

>
>
> 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:yves@zioup.com<xmpp%3Ayves@zioup.com>
>
>
>

v2.8.7 | Report a Bug | By Email