<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Thanks for your responses.<br><br>What is the syntax to make every word in the index clickable so one can navigate from index words to the text ?<br><br>Should we put instruction before each word in the index ?<br><br><p style="margin: 0px; text-indent: 0px;"> \hyperlink{\index}{Google} Recherche de \hyperlink{\index}{blogs} est l'application de la \hyperlink{\index}{technologie de recherche} Google aux blogs. Google est un fervent défenseur du mouvement d'auto-publication que représentent les blogs. Nous espérons que Google Recherche de blogs aidera nos utilisateurs.</p><br>or<br><br>There is something else to do.<br><br><br>Many thanks<br>Houda<br><br><br><br><br>> Date: Wed, 9 Mar 2011 08:47:57 -0500<br>> From: maxwell@umiacs.umd.edu<br>> To: xetex@tug.org<br>> Subject: Re: [XeTeX] hypertext index<br>> <br>> On Tue, 8 Mar 2011 23:12:54 -0500, Alan Munn <amunn@gmx.com> wrote:<br>> > I'm no expert on this, so I'd best stop while I'm ahead. Does makeindex<br>> > sort non-English things properly without resorting to special devices in<br>> > the index entries? Anyway, there is no problem as far as I know with<br>> > hyperref and makeindex; the problems with makeindex are related to its<br>> > ability to deal easily with non-English sort orders.<br>> <br>> Ok, that makes sense. In our case, sorting doesn't cause a problem,<br>> because the index entries I mentioned contained phonemic (linguistic,<br>> non-orthographic) representations, and there *is* no "right" way to sort<br>> them. (Fortunately for us, the index entries contain English text<br>> introducing them, so the sorting works on that, and any remaining ambiguity<br>> in sorting affects at most a few entries.) <br>> <br>> If on the other hand you were creating index entries for words written in<br>> an orthography for which there was s "correct" sort order, like a<br>> Perso-Arabic or Indic script language, then I would imagine that makeindex<br>> cannot know how to sort them. You can't even sort by the Unicode code<br>> points, since different languages using the same Unicode blocks can (and<br>> often do) have distinct sort orders. All this is explained in xindy's FAQ:<br>> http://xindy.sourceforge.net/doc/faq-1.html#ss1.1<br>> which I should have looked at first.<br>> <br>> <search for "unicode" at xindy site> Hmm, looks like the real problem with<br>> xindy is that it doesn't speak Unicode...there was a little discussion<br>> about changing it to be UTF-8 aware, but it's not clear that ever got done.<br>> So yes, I can see how that would be a problem! Similarly for BibTeX, I<br>> guess; we're using it successfully with XeLaTeX, but probably only because<br>> our use of Unicode in the citations is minimal, and we've been lucky.<br>> <br>> So yes, I see your point!<br>> <br>> Mike Maxwell<br>> <br>> <br>> --------------------------------------------------<br>> Subscriptions, Archive, and List information, etc.:<br>> http://tug.org/mailman/listinfo/xetex<br> </body>
</html>