Incorrect index sort order in Japanese

This forum is for all Flare issues related to PDF, eBook, Microsoft Word, Adobe FrameMaker, XPS, and XHTML book targets.
Post Reply
khirano
Jr. Propeller Head
Posts: 1
Joined: Tue Apr 06, 2010 10:51 pm
Location: Tokyo, Japan

Incorrect index sort order in Japanese

Post by khirano »

When I build a pdf target in Japanese, the sort order for index is incorrect ...
In Japanese, we should add the readings(kana) for Kanji characters.

For example,
<MS-Word field code>
{XE "Kanji-keyword" \y "kana"}

<Adobe Framemaker>
kanji-keyword[kana]

<DITA>
<indexterm>kanji-keyword<index-sort-as>kana</index-sort-as></indexterm>

I know the index keyword tag is "<MadCap:keyword term="Kanji-keyword" />",
however, I can not find the option parameter for readings(kana)....

If you have any idea, please help me.
You do not have the required permissions to view the files attached to this post.
Koji Hirano
Media Research Inc. (Tokyo, Japan)
pe_thiemann
Propeller Head
Posts: 32
Joined: Mon Jan 09, 2006 6:29 am
Location: Ottobrunn, Germany
Contact:

Re: Incorrect index sort order in Japanese

Post by pe_thiemann »

There is no answer yet, but we work on the same issue. So, is there a solution? Maybe an undocumented attribute for the Madcap:keyword tag? Or a workaround for manipulating the sort order according to Adobe?
Thanks for any help,
Regards,
_______________________________
Petra Thiemann
cognitas GmbH
München
Ramon-L10n
Jr. Propeller Head
Posts: 2
Joined: Tue Aug 27, 2024 1:28 am

Re: Incorrect index sort order in Japanese

Post by Ramon-L10n »

Greetings,

Although I have stealthily been checking this forum for some time, I signed up only last week.

I’ve been in the localization business since 1995, working on Flare localization projects during the last 7 years. In this role, I recently came across the same issue described here, which is why I’m rescuing this old thread for my first post.

Upon inquiring with their support team, Madcap confirmed a few days ago a bug regarding index sorting in Japanese and opened Bug Report #155973 for a potential fix in a future patch or release.

In the meantime, I documented and published my workaround at ramonortega.com/indexja in case it might be of any use.

Comments, rebukes, or questions welcome.

Ramon
Post Reply