Salut JC!

Jean-Christophe Helary wrote:
> Can't you ask your client to provide you with proper HTML stuff so
> that the handling of the CHM set is on their side and not on yours ?

I think that the translators should always compile their translated HTML Help
files into the final CHM format themselves. This is the only way one can make
sure the index is properly sorted and *tweaked*. I don't want series of
redundant entries to remain in my translated index.

This often happens when the same notion is worded in different ways so that the
users will have more chances to find what they're looking for in the index. When
such 'synonym' entries are translated they may end up starting with the same
word, or with the same letter, thus appearing consecutively in the translated
index. When this happens I always manually remove the redundant entries from the
index file -- they don't help the user; they only create unnecessary noise.

I always review the translated index and postedit it (partly in a text editor,
partly in MS Help Workshop).

Another MS HHW bug I forgot to mention in my previous message (to Herbert) is
that its manual index sort feature (the A/Z button) does not work well when you
have sets of second-level entries in the index that belong to different
first-level entries starting with the same word. You then need to move the
misplaced entries to their proper location (under their parent first-level
entry) manually. For instance, instead of:
meeting room
locating
scheduling
meeting
accepting
details
scheduling
viewing


sorting with the A/Z button produces:
meeting
meeting room
accepting
details
locating
scheduling
scheduling
viewing

Using the binary index options (set in the HHP file) produces a properly sorted
index, but it has another bug (see my previous message).

FWIW
Suzanne