<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Ross Moore wrote:<br>
<blockquote type="cite">
<pre wrap="">here is no incompatibility.
Just change the font-encoding away from the default of 'U',
whenever you encounter one of your active characters.</pre>
</blockquote>
Thanks for pointing that out. <br>
<br>
<blockquote type="cite">
<pre wrap="">You also need a declaration for how \d works
with the 'UX' encoding.
If this is the same as for T1 or T3 then you could
just use those instead.</pre>
</blockquote>
\d is identical in all font encodings, since it simply uses the glyph
"." in the current font.<br>
<br>
Jonathan Kew wrote:<br>
<blockquote type="cite">
<pre wrap="">BTW, in the latest xetex you can use the e-TeX style construction
\iffontchar\font"1E0D
in place of
\ifnum\XeTeXcharglyph"1E0D > 0
</pre>
</blockquote>
Good to know, thanks!<br>
<br>
<br>
Will Robertson wrote:
<blockquote
cite="mid27990a880607210216h667500dfrd07b68b5941e9cf0@mail.gmail.com"
type="cite">
<pre wrap="">Hi Francois,
(Sorry about the cedilla, but I'm on a windows machine at uni and
don't know how to type them!)
</pre>
</blockquote>
Don't worry, I'm used to that. Here in Germany people often spell my
name Francoise, which is slightly worse ;-) <br>
<blockquote
cite="mid27990a880607210216h667500dfrd07b68b5941e9cf0@mail.gmail.com"
type="cite">
<pre wrap="">
I can see situations where your package could be useful (nice name, by
the way). As a side note, I think it might be a good idea to write a
package to get LaTeX's \DeclareUnicodeCharacter working as expected --
note that it does the opposite thing to xunicode's
\DeclareUTFcharacter. To paraphrase myself from last November:
In xunicode, \textsection is defined as the unicode char "00A7:
\DeclareUTFcharacter[\UTFencname]{x00A7}{\textsection}
In utf8enc.dfu (for \usepackage[utf8]{inputenc}), the unicode char
"00A7 is defined as the macro \textsection:
\DeclareUnicodeCharacter{00A7}{\textsection}
(I think the similarities in names between these two macros is
confusing, but I'm not sure if you're willing, Ross, to change things
at this point. I'd also swap the arguments of \DeclareUTFcharacter for
similar reasons, if it were up to me.)
</pre>
</blockquote>
I agree, I was also confused by that. <br>
<blockquote
cite="mid27990a880607210216h667500dfrd07b68b5941e9cf0@mail.gmail.com"
type="cite">
<pre wrap="">
Anyway, I was saying that it would be good to provide a command
somewhere (maybe xltxtra?) along the lines of
\newcommand\DeclareUnicodeCharacter[2]{%
\catcode^^^^#1=\active
\DeclareCommand^^^^#1{#2}}
(Untested. Will that work?) A warning to prevent overwriting'd be good, too.
I'd also use this macro for things like
\DeclareUnicodeCharacter{**emdash**}{\unskip\,\textemdash\nobreak\,\ignorespaces}
or whatever.
</pre>
</blockquote>
Good idea: I had also tried something along these lines... but no, that
doesn't work :-( Once we have reimplemented that macro though, I think
it might be a good thing to integrate it to xltxtra instead of creating
yet another package. Perhaps xdiacomp then, once it comes to maturity,
could be better implemented as an option to the xltxtra package?
Ideally it should contain a large collection of "fallback macros"
(which can be put together from the data in D. Unruh's ucs package),
and it would be up to the user to decide which Unicode characters (or
even better, range of characters) should be made \active. For instance
by typing something like:<br>
<blockquote>\MakeUnicodeRangeActive{1D80}{1DBF}<br>
</blockquote>
the characters in the Block "Phonetic Extensions Supplement" would
become automagically active, and in the absence of the appropriate
glyphs in the font, their fallback macros (in this case via tipa's T3
encoding) would do the job of providing the glyphs. An additional
option could also make it possible to choose the preferred fontfamily
for that encoding (here ptm or cmr), depending of which one harmonizes
best with the default roman font. Another possibility, perhaps, would
be an option for declaring a second OpenType font as a fallback before
getting at the LaTeX macro, though in general this might not be really
advisable. <br>
<br>
Cheers,<br>
François<br>
</body>
</html>