Re: [dita-translation] FW: [dita] Groups - DITA 1.1: Block and inlineelements, plus translation info (elementsOnePointOne.html) uploaded

Hi,

I didn't get a c hance to create a polished
best practices document for multilingual content. But these are the initial
thoughts I came up iwith:

=================================================

Following are a proposed set of
best practices for sourcing content in DITA in order to publis it within
a single output document

Segregate source content by language

First of all, to the extent possible, use topic-sized chunks of content.
In this case,  each language should have it’s own topic, with file
names or reference names (in a CMS) annotated by language/locale

If you are using content that cannot possible be stored in a standalone
topic, you should review why this is so. If it’s because the content consists
of ‘fragment’ of content, scuh as product names, or phrases, modify it
to be complete sentence fragments, at the very least. For the most part,
there is no reason why any complete sentence fragment couldn’t have its
own topic, as long as the topic title can be ignored.

If the content simply can’t be
stored in its own topic,  store the chunks together in one or more
‘collection files’, each chunk with its own  ID string, so that
they can be conref’d from the primary source document as needed.  However,
every chunk should  consist of complete sentences, to enable appropriate
creation of TM

-  

==============================================================================

The issue I'm not so sure about is publishing
guidelines. I don't know just how some of the publishing pipeline work
to include multi-lingual content in a single, for example, PDF output stream.

Nancy

____

Nancy Harrison

IBM Rational Software

Phone: 781-676-2535



"JoAnn Hackos"
<> 

10/30/2006 10:30 AM

To

<>,
<>, <>, <>,
"Bryan Schnabel" <>, Charles Pau/Cambridge/IBM@Lotus,
<>, <>, Dave A Schell/Raleigh/IBM@IBMUS,
<>, <>, "Howard.Schwartz"
<>, "Jennifer Linton" <>,
<>, <>, <>,
<>

cc

Subject

[dita-translation] FW: [dita]
Groups - DITA 1.1: Block and inline elements, plus translation info  
(elementsOnePointOne.html) uploaded

Hello Everyone,

Andrzej is not able to make today's meeting. Let's discuss Robert's

additions to the inline elements for DITA 1.1 instead. Please download

the information.

JoAnn

> From:  [mailto:]

> Sent: Wednesday, October 04, 2006 1:29 PM

> To: 

> Subject: [dita] Groups - DITA 1.1: Block and inline elements, plus

> translation info (elementsOnePointOne.html) uploaded

>

> Related to the list of block vs. inline elements for DITA 1.0:

>

http://www.oasis-open.org/apps/org/workgroup/dita/download.php/18040/ele

> ments.html

>

> I noticed that the list was still missing all DITA 1.1 elements. This

> file

> includes all new OASIS 1.1 elements (barring any changes during

review),

> and should be merged with the original doc when approved.

>

>  -- Mr. Robert Anderson

>

> The document named DITA 1.1: Block and inline elements, plus

translation

> info (elementsOnePointOne.html) has been submitted by Mr. Robert

> Anderson

> to the OASIS Darwin Information Typing Architecture (DITA) TC document

> repository.

>

> Document Description:

> Related to the list of block vs. inline elements for DITA 1.0:

>

http://www.oasis-open.org/apps/org/workgroup/dita/download.php/18040/ele

> ments.html

>

> This file should be merged with the other when approved.

>

> View Document Details:

>

http://www.oasis-open.org/apps/org/workgroup/dita/document.php?document_

> id=20570

>

> Download Document:

>

http://www.oasis-open.org/apps/org/workgroup/dita/download.php/20570/ele

> mentsOnePointOne.html

>

>

> PLEASE NOTE:  If the above links do not work for you, your email

> application

> may be breaking the link into two pieces.  You may be able to
copy and

> paste

> the entire link address into the address field of your web browser.

>

> -OASIS Open Administration

>

>