Am Fri, 8 Jul 2011 15:29:21 +1000 schrieb Vafa Khalighi:
> Several users has reported that xetex and xelatex included in MikTeX 2.9
> (and perhaps MiKTeX 2.8) is buggy. The minimal document is:
>
> \documentclass{article}
> \usepackage{fontspec}
> \setmainfont[Script=Arabic,Mapping=parsidigits]{X
On Thu, Jul 7, 2011 at 10:08 AM, Ulrike Fischer wrote:
> Am Thu, 7 Jul 2011 12:13:21 +0200 schrieb Mojca Miklavec:
>
>
>> Thanks a lot for the answer. Actually, the looping itself is not a
>> problem. I was trying to modify Will Robertson's document
>> (http://mirrors.ctan.org/macros/latex/contri
Yes, in a charmap tool like babelmap, U+22D3 DOUBLE UNION and
U+22D2 DOUBLE INTERSECTION are confused (standing upside down?),
but blame STIXGeneral -- XITS just inherits the mistake.
if a student copies a wrong answer from another student, than that other
student is to blame and the first on
I'm creating some hyphenation rules for Jarai texts that I'm
interlinearizing. Here's the problem: In various texts, a complex character
such as LATIN SMALL LETTER A WITH BREVE might be encoded as a single code
point (U+0103) or as a combination of code points (LATIN SMALL LETTER A:
U+0061 plus COM
On Fri, 8 Jul 2011 15:00:42 -0500, Joshua and Amy
wrote:
> I'm creating some hyphenation rules for Jarai texts that I'm
> interlinearizing. Here's the problem: In various texts, a complex
character
> such as LATIN SMALL LETTER A WITH BREVE might be encoded as a single
code
> point (U+0103) or as a
So, I guess I was foolish to hope that Google has figured out how to return
results that have non-identical but equivalent strings?
I hope it's not too off-topic for this list, but can you point me to any
good resources on normalization (is there a straightforward automation for
someone who doesn'
Unicode normalization was discussed on this list a couple of months ago.
Phil Taylor provided a small program to do the job, and other utilities were
referred to. There's also a command within XeTeX that normalizes unicode
before passing it to TeX's digestion. Try this in your header:
% Normali
On Fri, 8 Jul 2011 15:50:07 -0500, Joshua and Amy
wrote:
> So, I guess I was foolish to hope that Google has figured out how to
return
> results that have non-identical but equivalent strings?
I'm sure google has figured this out, and some programs to an automatic
conversion to composed or decomp
This is a better answer than mine, so disregard my noise. But I do have a
question below:
On Fri, 8 Jul 2011 23:13:41 +0200, Dominik Wujastyk
wrote:
> ...
> There's also a command within XeTeX that normalizes unicode
> before passing it to TeX's digestion. Try this in your header:
>
> % Norma
On 8 Jul 2011, at 23:24, maxwell wrote:
> I found \XeTeXinputnormalization in XeTeX documentation, but I'm not
> familiar with the other two commands. I guess \tracingonline=1 means to
> output errors to stdout (or stderr?), but where is the effect of
> \tracinglostchars described?
See The TeXbo
Many, thanks, all, and sorry for missing the earlier discussion.
But back to my original question, is there a way to get \hyphenation to
require only one form and the rest come for free?
On Fri, Jul 8, 2011 at 5:37 PM, Jonathan Kew wrote:
> On 8 Jul 2011, at 23:24, maxwell wrote:
>
> > I found \
11 matches
Mail list logo
