> Could it be possible you have two copies of IPAMincho in your
> system/texpath right now? This has been known to result in issues such
> as incorrect glyphs showing up in the output, as in your case.
I did have a meta-font varient installed from an earlier iteration of things
when I was using t
Could it be possible you have two copies of IPAMincho in your
system/texpath right now? This has been known to result in issues such
as incorrect glyphs showing up in the output, as in your case.
--
Subscriptions, Archive, and List information, etc.
Hi
I'm not sure what reversing you get (the whole link? individual letters?),
but in case it helps here is some antediluvian code that I used to use many
years ago to get occasional Hebrew words in ordinary EmTeX. You would want
to put the back-to-front text in the \reversedtext macro at the
>
> So this could be replaced (just for this font). This is not a general
solution, since the \XeTeXglyph command is completely font dependent.
> \newcommand{\sdol}{{\XeTeXglyph 452}}
Really appreciate the responses. XeTeXglyph wrapped in a command is
precisely what I needed. Cheers!
--
On Fri, Aug 20, 2010 at 04:51:45PM +0300, Ron Aaron wrote:
> On Friday 20 August 2010 16:15:22 Khaled Hosny wrote:
> > On Fri, Aug 20, 2010 at 03:11:15PM +0200, Ulrike Fischer wrote:
> > > Am Fri, 20 Aug 2010 13:57:46 +0300 schrieb Ron Aaron:
> > > > Yes, well that is exactly the problem I am tryin
On Friday 20 August 2010 16:15:22 Khaled Hosny wrote:
> On Fri, Aug 20, 2010 at 03:11:15PM +0200, Ulrike Fischer wrote:
> > Am Fri, 20 Aug 2010 13:57:46 +0300 schrieb Ron Aaron:
> > > Yes, well that is exactly the problem I am trying to find a way to
> > > work-around!
> >
> > I did understand th
On Fri, Aug 20, 2010 at 03:11:15PM +0200, Ulrike Fischer wrote:
> Am Fri, 20 Aug 2010 13:57:46 +0300 schrieb Ron Aaron:
> > Yes, well that is exactly the problem I am trying to find a way to
> > work-around!
>
> I did understand this ;-). But if the author of bidi didn't find a
> solution to the
Am Fri, 20 Aug 2010 13:57:46 +0300 schrieb Ron Aaron:
>> I don't see why you need your own code. The following links looks
>> identical for me:
> Of course they do. But as I mentioned, I am not using xelatex but
> xetex -- and for whatever reason, the hyperref package does not
> completely wo
On Fri, Aug 20, 2010 at 04:06:18PM +0300, Ron Aaron wrote:
> On Friday 20 August 2010 15:37:00 Khaled Hosny wrote:
>
> > So, in the eye of the dvi driver, comes first so it does
> > nothing, and is runaway. Bidi package has some work around
> > for that, but it can't work around line breaks.
>
On Friday 20 August 2010 15:37:00 Khaled Hosny wrote:
> So, in the eye of the dvi driver, comes first so it does
> nothing, and is runaway. Bidi package has some work around
> for that, but it can't work around line breaks.
Thank you very much, Khaled, for the detailed answer.
At least I have
Am Fri, 20 Aug 2010 20:39:12 +0900 schrieb Andrew A. Adams:
>>> I recently upgraded my Fedora Core 10 to Fedora Core 13. I'm getting a very
>>> strange behaviour from processing latex files including Japanese text and
>>> processed using xelatex. I've created a minimal input source file which
On Fri, Aug 20, 2010 at 08:09:30PM +0900, Andrew A. Adams wrote:
> > The Kanji_Test.tex file you attached is encoded in UTF-16. I'm
> > surprised you got output of any kind using the file as is.
>
> Ah, I was just messing around with the xemacs side of things and obviously
> hadn't re-set that. H
On Fri, Aug 20, 2010 at 02:20:52PM +0200, Khaled Hosny wrote:
> On Fri, Aug 20, 2010 at 09:09:31AM +0300, Ron Aaron wrote:
> > On Wednesday 18 August 2010 23:06:02 Ron Aaron wrote:
> > > Using xetex I found that the 'hyperref' package did not product
> > > attractive links in PDF, so I had to writ
** Andrew A. Adams [2010-08-20 20:09:30 +0900]:
>> The Kanji_Test.tex file you attached is encoded in UTF-16. I'm
>> surprised you got output of any kind using the file as is.
>
> Ah, I was just messing around with the xemacs side of things and obviously
> hadn't re-set that. Here's the utf-8 ve
On Fri, Aug 20, 2010 at 09:09:31AM +0300, Ron Aaron wrote:
> On Wednesday 18 August 2010 23:06:02 Ron Aaron wrote:
> > Using xetex I found that the 'hyperref' package did not product attractive
> > links in PDF, so I had to write my own PDF link code:
>
> This seems to be specifically a "dvipdfmx
> Am Fri, 20 Aug 2010 13:06:27 +0900 schrieb Andrew A. Adams:
>
> > I recently upgraded my Fedora Core 10 to Fedora Core 13. I'm getting a very
> > strange behaviour from processing latex files including Japanese text and
> > processed using xelatex. I've created a minimal input source file whic
> The Kanji_Test.tex file you attached is encoded in UTF-16. I'm
> surprised you got output of any kind using the file as is.
Ah, I was just messing around with the xemacs side of things and obviously
hadn't re-set that. Here's the utf-8 version, which produced the same problem
in the first plac
On Friday 20 August 2010 13:36:36 Ulrike Fischer wrote:
> Am Wed, 18 Aug 2010 23:06:02 +0300 schrieb Ron Aaron:
>
> I don't see why you need your own code. The following links looks
> identical for me:
Of course they do. But as I mentioned, I am not using xelatex but xetex -- and
for whatever r
Am Wed, 18 Aug 2010 23:06:02 +0300 schrieb Ron Aaron:
> Using xetex I found that the 'hyperref' package did not product
> attractive links in PDF, so I had to write my own PDF link code:
I don't see why you need your own code. The following links looks
identical for me:
\documentclass{article}
\
Am Fri, 20 Aug 2010 13:06:27 +0900 schrieb Andrew A. Adams:
> I recently upgraded my Fedora Core 10 to Fedora Core 13. I'm getting a very
> strange behaviour from processing latex files including Japanese text and
> processed using xelatex. I've created a minimal input source file which
> demon
On 2010-08-18 19:24:01 +0930, "M. Niedermair"
said:
Is there a way to display with fontspec all supported features of a
special font?
No (eventually planned), but you can use the opentype-info.tex
"document" to do this.
Are all standard otf feature mapped to fontspec-parameters?
If not
Hi,
When I open your file in gedit, I get an error message that the file is not in
UTF-8 and cannot be opened with any of the "default encodings". If I switch to
UTF-16 manually I can open the file but it looks very strange: there are no
control sequences, and while CJK characters show up, they
On Friday 20 August 2010 09:41:14 Ross Moore wrote:
> Hi Ron,
>
> On 20/08/2010, at 4:09 PM, Ron Aaron wrote:
>
> > On Wednesday 18 August 2010 23:06:02 Ron Aaron wrote:
> >> Using xetex I found that the 'hyperref' package did not product attractive
> >> links in PDF, so I had to write my own PD
23 matches
Mail list logo
