On Fri, Aug 02, 2013 at 11:13:44AM +0800, Kai Hendry wrote:
> IIUC `fc-list :lang=kr : family` gives me the font names that cover Korean
> IIUC.
The ISO language code for Korean is ko.
Regards,
Khaled
--
Subscriptions, Archive, and List informati
On 1 August 2013 22:54, Peter Dyballa wrote:
> Specific for the script to be used, provided it has support for the language
> in use: http://www.wazu.jp/
So has no one has done the mapping of:
$_SERVER["HTTP_ACCEPT_LANGUAGE"] - Web browser's preconfigured
language setting IIUC
texlive-* - Debi
2013/7/31 Akira Kakuto :
> Hi,
>
>> Is it possible to find which
>> exact font file was used by XeTeX and which one by xdvipdfmx?
>
>
> I think, in the recent XeTeX, used font files are written with full paths
> in foo.xdv by xe(la)tex --no-pdf foo.
>
Thank you very much for this note. Although I h
On Fri, Aug 02, 2013 at 12:40:28PM +0200, Georg Duffner wrote:
> Am 01.08.2013 13:24, schrieb Khaled Hosny:
> >On Thu, Aug 01, 2013 at 12:06:43PM +0200, Georg Duffner wrote:
> >>Hi,
> >>
> >>XeTeX’s behaviour in this case is mysterious.
> >>
> >>I tried Mike’s original tex file and got no smallcaps
On Fri, Aug 02, 2013 at 10:49:57AM -0400, maxwell wrote:
> So Windows happily installed both versions of this font in
> C:\Windows\Fonts\, because the two versions had different file names.
In my experience, windows always keeps the old file(s) under different
names, even though it will pop up a m
On 2013-08-02 10:38, Lorna Evans wrote:
In my case (I'm the OP), the problem indeed turned out to
be with my font files--I had two versions of the CharisSIL
font files, with slightly different names. Apparently it
(Cygwin, and therefore XeLaTeX) was picking up the older
ones, which were known to
On 2013-08-02 06:40, Georg Duffner wrote:
I tried to reproduce the above behaviour by deleting and adding
different versions – without success.
In my case (I'm the OP), the problem indeed turned out to be with my
font files--I had two versions of the CharisSIL font files, with
slightly diff
On 2013-08-02 06:40, Georg Duffner wrote:
I tried to reproduce the above behaviour by deleting and adding
different versions – without success.
In my case (I'm the OP), the problem indeed turned out to be with my
font files--I had two versions of the CharisSIL font files, with
slightly differ
Am 01.08.2013 13:24, schrieb Khaled Hosny:
On Thu, Aug 01, 2013 at 12:06:43PM +0200, Georg Duffner wrote:
Hi,
XeTeX’s behaviour in this case is mysterious.
I tried Mike’s original tex file and got no smallcaps at all. After
updating Charis to 4.114 (from 4.106) I got the same behaviour as
him:
