OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-comment] Small issues with the DITA standard


Hi Radu,

> The existing xml:lang attribute cannot be used to profile and filter out content. In the past we had users somehow mixing languages in the same DITA Map and expecting to output either for one language or the other by filtering out based on the xml:lang attribute.

I think it is not the suitable idea to use xml:lang for filtering. As specification says, xml:lnag attribute explicitly define the language of the under-laying contents.

2.4.6.1 The @xml:lang attribute
http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/archSpec/base/xmllang.html#xmllang

> The @xml:lang attribute specifies the language and (optional) locale of the element content.

In my understanding there is actually multiple language DITA documents. For instance English document for Chinese (PRC) sometimes contains Chinese sentences that corresponds 国家标準(Country Standard). In this case the paragraph is marked partially as @xml:lang="zh-CN" The appropriate stylesheet should .assign Chinese font for it in PDF output. (PDF5-ML does it automatically)

If you want to apply filtering for the contents, it should be done by the delivery destination in most cases not by the language. One of my user does not use CMS and they want use different images in topics by shipping country. To sort out this challenge I've introduced "deliveryDestination" by specialization of the "props" attribute. Currently it is used as following and works fine.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//ACME//DTD DITA Map//EN" "map.dtd" [
<!ENTITY image-rel-path "../image/">
]>
<map>
   ...
    <keydef keys="IMG_016" href="&image-rel-path;016_en.png" deliveryDestination="CHN TWN USA FRA DEU ITA KOR PRT ESP" format="png" type="image"/>     <keydef keys="IMG_016" href="&image-rel-path;016_ja.png" deliveryDestination="JPN" format="png" type="image"/>     <keydef keys="IMG_017_01" href="&image-rel-path;017_01.gif" format="gif" type="image"/>     <keydef keys="IMG_017_01_1" href="&image-rel-path;017_01_1_en.png" deliveryDestination="CHN TWN USA FRA DEU ITA KOR PRT ESP" format="png" type="image"/>
   ...
</map>

The specialization sample is here:

AntennaHouse/ah-dita
https://github.com/AntennaHouse/ah-dita/blob/master/com.antennahouse.dita.dita13.doctypes/doctypes/dtd/base/dtd/deliveryDestinationAttDomain.ent


Hope this helps your understanding.

Regards,


On 2017/09/15 16:35, Radu Coravu wrote:
Hi everybody,

I wrote a small blog post listing some of the DITA standard-related issues our clients have been having during these years:

http://blog.oxygenxml.com/2017/09/small-problems-with-dita-standard.html

You probably know about most of these though.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


--
/*--------------------------------------------------
 Toshihiko Makita
 Development Group. Antenna House, Inc. Ina Branch
 E-Mail tmakita@antenna.co.jp
 8077-1 Horikita Minamiminowa Vil. Kamiina Co.
 Nagano Pref. 399-4511 Japan
 Tel +81-265-76-9300 Fax +81-265-78-1668
 Web site:
 http://www.antenna.co.jp/
 http://www.antennahouse.com/
 --------------------------------------------------*/



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]