Hi Wilfred,
The Korean hangul script is already phonetic, so it does not need ruby. Kanji
are used in Korea, but mostly to indicate place names and family names.
Yeah, hence phonetic guide text (so, text that accompanies chinese
characters), not just phonetic text. You can still stick ha
On Sat, Jul 24, 2010 at 8:35 AM, tala...@fastmail.fm wrote:
> Dear all,
>
> I'm using XeLaTeX (with memoir, fontspec, & polyglossia). I have typeset my
> document in Lotus Linotype. The problem is that the quotation marks I have
> typed in are not appearing in the output. When I switch the font to
footnote mechanism in bidi is pretty complex and it almost provides
everything you need. We can not support every single footnote package in
bidi. So you can not expect that ednote package works perfectly with bidi
unless its author has done some bidi-aware macro programming. bidi gives you
absolut
Dear all,
I am using Ednotes & Polyglossia (and thus Bidi) to produce a critical edition
of an
Arabic text, in Memoir. Ednotes seems to call up the manyfoot package
automatically. I am having two problems:
1. I have three levels of footnotes. I want each footnote stream (A,
B, C) to have a d
Dear all,
I'm using XeLaTeX (with memoir, fontspec, & polyglossia). I have typeset my
document in Lotus Linotype. The problem is that the quotation marks I have
typed in are not appearing in the output. When I switch the font to
Scheherazade, the quotation marks appear correctly.
I am sure it
Hi,
> used in Taiwan. I am not aware of any phonetic guide text
> practices in Korea.
The Korean hangul script is already phonetic, so it does not need ruby. Kanji
are used in Korea, but mostly to indicate place names and family names.
The hangul script combines 1, 2, or 3 consonants and vowel
Hi all,
As Francois Charette has indicated in another email, there are already two
packages for Japanese with polyglossia. I have offered to make these packages
into "official" polyglossia releases because the present versions are adaptions
from adaptions (I live in Japan, I can speak enough Ja
On 7/23/2010 1:02 PM, Philip Taylor (Webmaster, Ret'd) wrote:
Just one comment, since we seem to be converging on agreement :-)
Gerrit wrote:
I don’t think that there is Ruby used in academic writings in Taiwan.
It all depends what you mean by "academic" : Ruby is most certainly
used in text
This kind of sounds like a job for a massively huge tome of knowledge:
http://oreilly.com/catalog/9780596514471 (CJKV Information Processing,
Second Edition)
- Mike
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman
On 23/07/2010 17:15, Gerrit wrote:
Hello!
I will try to gather some information about Japanese, Chinese and Korean support for
Polyglossia in the next days.
Because I do not understand tex programming at all, I can only give some information
here. I will try to write it as detailled as poss
Just one comment, since we seem to be converging on agreement :-)
Gerrit wrote:
I don’t think that there is Ruby used in academic writings in Taiwan.
It all depends what you mean by "academic" : Ruby is most certainly
used in texts used to teach the Chinese language to children, which
some mi
Am 24.07.2010 02:22, schrieb Philip Taylor (Webmaster, Ret'd):
Gerrit wrote:
Hello Philip,
what I meant for simplified Chinese as being easy is because of this:
- it is also only written horizontally
- no ruby characters (at least as I know)
- uses arabic digits (e.g. 2010年)
Definitely not
Gerrit wrote:
Hello Philip,
what I meant for simplified Chinese as being easy is because of this:
- it is also only written horizontally
- no ruby characters (at least as I know)
- uses arabic digits (e.g. 2010年)
Definitely not the last : I know of many instances
of simplified Chinese that
Hello Philip,
what I meant for simplified Chinese as being easy is because of this:
- it is also only written horizontally
- no ruby characters (at least as I know)
- uses arabic digits (e.g. 2010年)
Ok, maybe my axioms for Korean were not really that good.
The alphabet part is actually of no im
Maybe ditch MikTeX ? The version of XeTeX that comes
with TeX Live 2010 pre-test (and accompanying support files)
doesn't manifest this bug.
Philip Taylor
Стас Фомин wrote:
Sorry, but if there is any workaround/patch for the bug?
2010/6/21 Стас Фомин mailto:stanislav.fo...@gmail.com>>
Sorry, but if there is any workaround/patch for the bug?
2010/6/21 Стас Фомин
> Hello all!
>
> I have full installation of Miktex 2.8.
> This is my minimal working sample:
>
> ---
> \documentclass{beamer}
> \XeTeXdefaultencoding "UTF-8"
> \begin{document}
> \end{document}
>
> ---
Gerrit wrote:
I think, Korean is really easy to implement. As far as I know, modern
Korean typography is almost the same as western typography:
- it has word spacing
- uses an alphabet (ok, sometimes Chinese characters in between, but
that is not really a problem) with no fancy effects unlike
No problem. I also don’t understand everything.
I think, Korean is really easy to implement. As far as I know, modern
Korean typography is almost the same as western typography:
- it has word spacing
- uses an alphabet (ok, sometimes Chinese characters in between, but
that is not really a pro
See Mike's answer to me. I had been reading the fontspec docs recently
and wasn't sure if you had looked at them. But I know very little about
CJK; as often, a little knowledge turns out to be a dangerous thing.
David
Gerrit wrote:
Hello David,
great, thank you for the answer. I checked th
Hello David,
great, thank you for the answer. I checked the documentation, but did
not completely understand the ruby option.
For good typesetting with ruby it is necessary that the ruby characters
appear thicker. They should not just be half the size of the base
character. As far as I know,
David,
Ruby is already enabled (if you are using a font that supports it).
See the fontspec package documentation. Fontspec also allows you to
select a number of other options relevant to CJK typesetting -- take a
look. (It doesn't address all the issues you raise, though.)
The ruby openty
Am 23.07.2010 um 11:21 schrieb Ernest Adrogué:
This is what I get:
$ fc-list : file family fullname | grep -i beteckna
/usr/share/fonts/truetype/beteckna/
BetecknaLowerCaseItalicCondensed.ttf:
BetecknaLowerCase:fullname=BetecknaLowerCase
/usr/share/fonts/truetype/beteckna/BetecknaLowerCaseI
Hi Gerritt,
Ruby is already enabled (if you are using a font that supports it). See
the fontspec package documentation. Fontspec also allows you to select
a number of other options relevant to CJK typesetting -- take a look.
(It doesn't address all the issues you raise, though.)
David
Hello!
I will try to gather some information about Japanese, Chinese and Korean
support for Polyglossia in the next days.
Because I do not understand tex programming at all, I can only give some
information here. I will try to write it as detailled as possible, so
that the implementation sho
> Hi!
>
> Is it possible to generate fake old-style figures & small
> capitals for fonts missing these glyphs with XeTeX.
> I used to use the mathpoz package that does exactly that,
> but something tells me it's not compatible with XeTeX.
I guess it's the "mathpazo" package, for Palatino. You ca
Hi,
23/07/10 @ 10:27 (+0200), thus spake Peter Dyballa:
>
> Am 23.07.2010 um 02:30 schrieb Ernest Adrogué:
>
> >I am experiencing some problems with certain fonts.
> >First, with a font called Beteckna. Bold face and
> >italics don't work (are replaced with medium weight
> >and upright shape). T
Hi!
Is it possible to generate fake old-style figures & small
capitals for fonts missing these glyphs with XeTeX.
I used to use the mathpoz package that does exactly that,
but something tells me it's not compatible with XeTeX.
Cheers.
Ernest
--
Su
Am 23.07.2010 um 02:30 schrieb Ernest Adrogué:
I am experiencing some problems with certain fonts.
First, with a font called Beteckna. Bold face and
italics don't work (are replaced with medium weight
and upright shape). There are no error messages.
According to fontconfig bold and italics shou
28 matches
Mail list logo
