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 PDF link code:
>
> This seems to be specifically a "dvipdfmx" probl
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.
However, if you're sure the file is UTF-8 on your end, try the
following, maybe inputenc is the culprit:
\documentclass{article}
\usepackage{fontspec}
\begin{document}
\fontsp
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" problem, as using "etex" on the
sample I gave, followed by "dvipd
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
demonstrates the problem, which is that the unicode characters in the inp
Am 19.08.2010 um 16:51 schrieb Alan Munn:
> On Aug 18, 2010, at 1:44 PM, chagrins wrote:
>
>> With Adobe Garamond Pro, when I use
>>
>> \defaultfontfeatures{Numbers={Proportional,OldStyle}}
>>
>> ...it also outputs "lowercase" symbols - for example, the dollar sign
>> matches the numbers.
>>
On 08/18/2010 01:44 PM, chagrins wrote:
> With Adobe Garamond Pro, when I use
>
> \defaultfontfeatures{Numbers={Proportional,OldStyle}}
>
> ...it also outputs "lowercase" symbols - for example, the dollar sign
> matches the numbers.
>
> However, in Hoefler Text, I can't get the symbols to match
On 18/08/2010 06:10, Will Robertson wrote:
On 2010-08-12 16:16:54 +0930, Khaled Hosny said:
Ah, thank you. Are these features (relatively) new? Rather
embarrassing not to have spotted them, but anyway…
All were introduced in version 2, I think.
Yep, very new.
I've got a problem using the
On Aug 19, 2010, at 10:51 AM, Alan Munn wrote:
On Aug 18, 2010, at 1:44 PM, chagrins wrote:
With Adobe Garamond Pro, when I use
\defaultfontfeatures{Numbers={Proportional,OldStyle}}
...it also outputs "lowercase" symbols - for example, the dollar sign
matches the numbers.
However, in Hoefle
Am 18.08.2010 um 17:10 schrieb Lomky:
Are there other ways to convert it to utf8?
GNU Emacs, the recode utility, using a backup of the original
unchanged file...
--
Greetings
Pete
"Debugging? Klingons do not debug. Our software does not coddle the
weak."
---
On Aug 18, 2010, at 1:44 PM, chagrins wrote:
With Adobe Garamond Pro, when I use
\defaultfontfeatures{Numbers={Proportional,OldStyle}}
...it also outputs "lowercase" symbols - for example, the dollar sign
matches the numbers.
However, in Hoefler Text, I can't get the symbols to match the numb
Khaled Hosny wrote:
'otfinfo' tool reports font names and other info in a more clear way (I
can't tell from this shot what is what, I can only guess).
Thank you! Otfinfo does indeed produce more verbose answers :
C:\Fontin-Sans>otfinfo -i fontin_sans_bi_45b.otf
Family: Fontin
On Thu, Aug 19, 2010 at 07:02:57AM +0100, Philip Taylor (Webmaster, Ret'd)
wrote:
>
>
> Joel C. Salomon wrote:
>
> >Well, the font name (as opposed to the font file name) is “Fontin Sans”,
> >and it comes in many styles.
>
> Curiouser and curiouser (said Alice). I obtained my font
> names by
Am Wed, 18 Aug 2010 11:10:37 -0400 schrieb Lomky:
>> If really all text is ISO 8859-6, i.e., the 7-bit codes are Latin and AC-F2
>> are Arabic, then just convert the file's contents from ISO 8859-6 to UTF-8!
> This seems to work, but keeps hitting snags where I get the error 'illegal
> input s
Thanks for your suggestions Khaled and Pete.
I guess I'll just alter the fontfeatures when needed. Polyglossia and
the bidi package are already in use for hyphenation, language switching etc.
Best,
Volker
On 08/18/2010 03:34 PM, Peter Dyballa wrote:
Am 18.08.2010 um 13:31 schrieb Volker Haa
14 matches
Mail list logo
