Hi,
I thinking Eliot, you may be stretching the circumstances and overstating
the case. Technical communications documents have been happily produced
from DITA into Japanese for years with no need for Ruby. Ruby is not
essential for Japanese documents at least with PDF etc. publications.
My understanding from Translation SC discussions before 1.2 is that Ruby
is chiefly used in schoolbooks. Now we have the note from Tetsuya Sekine
that mentions several important issues, possibly connected with ebooks.
I've copied his note here for those who did not see it.
I think it's really important that we not overstate or misrepresent the
case.
I invite all members of the DITA Translation Subcommittee to comment in
this thread.
Thanks, JoAnn
JoAnn T. Hackos, PhD
President
Comtech Services Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
303-232-7586
Hi all,
I was already discussed some of you, regarding Ruby functionality.
Only problem is that meeting is held during the time, I am not usually be
able to attend.
I discussed this issue with some colleagues in the field.
1.Currently, most of the users and information developers are not
necessary needing Ruby.
WHY: Because in Technical Communication, this does not have much impact on
current targeted audiences (Paper, PDF, Online Help)
HOWEVER: From the point of accessibility and computer-voiced instructions
feature especialy to the new deliverables such as smartphone, Ruby will be
needed.
2.Rendition part is already supported by tools like AH XSL Formatter, and
the same things applied with current HTML browser and its standard
(HTML5/CSS3).
3.DITA adaption for the commercial publishing definitely needs Ruby, so
this can contribute DITA to be adapted more in that field, in conjunction
with ePub.
4.It is not a good way to extend Ruby as the Japanese own specialized
implementation because this action is against open standard.
(From my own experiences, Japanese have a tendency to come up with own
domestic standard and make things complicated, not align with the standard)
PS
In addition to Ruby, we want to have the similar elements as used in
<indexterm>/<index-sort-as> for glossary entries, in order to sort from
"yomigana"
One of our customers decided to specialize in order to have sorting in
glossary
As said enough,
I am for the Eliot, Nancy's proposal for standardization in DITA data
model, align with HTML5 and ePub etc.
Tetsuya Sekine
======================================================================
Tetsuya Sekine
President, Principal Consultant
InfoParse, Inc.
<your one stop DITA contact/>
<DITA + />
*email: | Skype <callto://tetsekine>
*url: www.infoparse.com | phone: 81 3-3736-8180
On 2/2/12 3:42 PM, "Eliot Kimber" <> wrote:
