On 29/07/2010 10:02, Ulrike Fischer wrote:
As Fabian has described he has changed flashcard.cls in two places
to get around the problems with the new geometry.
We had a discussion about this on the texlive mailing list last week. I would suggest
Fabian to upload his patched version of flashca
On 24/07/2010 18:13, David Perry wrote:
Can anyone see what's wrong with the following minimal example? (A bit long, I know,
but I trimmed it as much as I could.) It's probably something silly but I just can't see
it. I get all kinds of "undefined control sequences" and so forth when I compil
On 25/07/2010 19:43, Alan Munn wrote:
and the ednotes package is about the worst documented package I've ever seen,
Well, I've seen worse! But your statement in only true insofar as standard documentation
is concerned. The TUGboat article is quite acceptable however:
http://www.ctan.org/tex-
On 24/07/2010 19:09, David Perry wrote:
Vafa Khalighi wrote:
Is not \newfontfamily\greekfont{} and \newfontfamily\hebrewfont{} missing?
I did not think this was necessary, because the polyglossia manual
(section 4) says "For instance, if the default roman font defined by
\setromanfont does
On 24/07/2010 18:19, Vafa Khalighi wrote:
Is not \newfontfamily\greekfont{} and \newfontfamily\hebrewfont{} missing?
DejaVu contains both scripts, so the font setup for both should occur automatically. The
issue is something else. I'll investigate this later tonight.
FC
-
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
On 20/07/2010 09:29, Ulrike Fischer wrote:
(Languages are not symmetric regarding fonts: For latin scripts you
need normally 3 font families (for \rmfamily, \sffamily, \ttfamily)
while greek seems to use only one.)
There are Greek, Arabic and Hebrew fonts that can be used to match \sffamily a
10.17.1
Typo: TRK is the tag for Turkish in OpenType; tur is the ISO tag. (See
http://www.microsoft.com/typography/otspec/ttoreg.htm)
Yet many "real-world" OT fonts mistakenly use TUR instead of TRK for Turkish, hence in
this particular case fontspec needs to check for both when "Language=
On 19/07/2010 21:10, David Perry wrote:
I've been reading 10.17 (version of July 11, 2010) and have some questions, and found
one typo.
I will let Will comment on your interesting feedback. I only have a few minor observations
below.
10.17 (the very beginning)
It would be helpful to have
On 18/07/2010 08:40, Yves Codet wrote:
Hello.
With XeLaTeX, if you use the package "polyglossia", hyphenation patterns (included in
the package "hyph-utf8") corresponding to the language you select will be applied. For
instance:
\usepackage{fontspec}
\usepackage{polyglossia}
\setdefaultlang
On 18/07/2010 11:29, Vafa Khalighi wrote:
Its me with my problems again. Sorry
I have a problem in typesetting an English Book, the default language
is English and I have
\setotherlanguage{arabic}
Because of this above command, my page headings become RTL even
though
On 18/07/2010 07:44, Yusuf Mitha wrote:
Hi.
Its me with my problems again. Sorry
I have a problem in typesetting an English Book, the default language
is English and I have
\setotherlanguage{arabic}
Because of this above command, my page headings become RTL even
thought Arabic is not the Def
On 14/07/2010 15:51, William Adams wrote:
On Jul 14, 2010, at 9:45 AM, François Charette wrote:
The edition itself should indeed be searchable, indexable and the accompanying
apparatus should provide clear evidence for all changes the editor(s) made to
the original source(s). The
On 14/07/2010 15:31, Peter Baker wrote:
I love it! I'll try to get a look at his stuff.
Some of Boncompagni's earlier publications are on Google Books, but they are still
comparatively conservative in terms of "authentic reproduction". That became more visible
in the later issues of his Bul
On 14/07/2010 14:24, William Adams wrote:
On Jul 14, 2010, at 6:16 AM, François Charette wrote:
Still, I cannot refrain from asking: what is exactly the point of such fonts?
Any edition of an historical text should be first and foremost legible and
intelligible to modern readers, without
On 12/07/2010 19:38, Peter Baker wrote:
On 07/12/2010 11:44 AM, Will Robertson wrote:
If you typeset the word λόγου with and without 'hist' you will see
a difference.
Thanks for the suggestion; unfortunately I think these fonts only have historical
ligatures (hlig) rather than historical a
On 13/07/2010 22:46, Khaled Hosny wrote:
On Tue, Jul 13, 2010 at 10:07:54PM +0200, François Charette wrote:
If someone is able to translate the caption strings, that would be nice!
I don't speak Armenian myself, but keeping the English caption in the
file will allow others to know what
thur: is "hyphenmins={2,2}" (for left and right, resp.) okay for Armenian?
Regards,
François Charette
PS: the attached file cannot be used with polyglossia v1.1.1. You need to get v1.2 from
github:
http://github.com/fc7/polyglossia/archives/1.2
but the easiest is to wait for its app
On 13/06/2010 22:33, enrico.grego...@univr.it wrote:
Daron Wilson writes:
I'm using the XeLaTeX on Mac OS X 10.6, with MacTeX 2009
installed. According to the TeXLive Utility that comes with
MacTeX 2009, all the packages installed are up to date
I've been working on typesetting a document
On 08/06/2010 15:21, Will Robertson wrote:
Dear all,
The recently released version 2 of fontspec now clashes with polyglossia,
because the internals of fontspec have changed.
polyglossia was previously hooking into low-level macros to perform what is now
provided by a fontspec programming int
On 31/05/2010 12:35, Vadim Radionov wrote:
Vladimir,
You know, that Russian babel short-hands do slightly more than just insert a
glyph from the font: they adjust the spacing around the em-dash (and the
length of the dash, too), and allow hyphenation of adjacent words (in case
of hyphens). So e
On 14/05/2010 08:11, Nathan Camillo Sidoli wrote:
For some reason, this is only happening within footnotes. Within the
footnote, even changing the catcodes inside a group is not working.
It used to work for me... but maybe I was just lucky.
Please file a bug report at http://github.com/fc7/ara
On 05/05/2010 15:12, Florian Grammel wrote:
I've come across two minor oddities in polyglossia (1.1.1 tested on
MacTeX/TexLive2009 and on TeXLive 2009 GNULinux), which look like bugs to me:
a) Using the polyglossia-command \textitalian{} inserts an extra space, other
\text...{}-commands don't.
On 16/04/2010 15:35, Peter Davis wrote:
Am 15.04.2010 22:34, schrieb Peter Davis:
I'm trying to compile the polyglossia sample file,
test-polyglossia-setup.tex
??
Has this file really made it to CTAN? Hmm, then this happened by mistake
when producing the TDS archive. Sorry.
It was never in
For computational linguistic applications, where the wrong word boundary
results in a mis-parse, I believe that finding "correct" word boundaries is
still a research problem, and cannot be solved by dictionary lookup alone.
For Thai, which is (I believe) similar to Lao in this respect, you might
On 13/03/2010 09:40, kevin & siji wrote:
Hi Fran?ois Charette,
I have prepared Tamil and Malayalam supporting files for
polyglossia/XeTeX. Can you please add them to the distribution.
The list of files attached are:
1. gloss-malayalam.ldf
2. hyph-ml.tex
3. loadhyph-ml.tex
4. gloss-tamil.ldf
On 09/03/2010 00:24, Wilfred van Rooijen wrote:
Could you contact the maintainers of gloss-japanese and gloss-nihongo? Maybe
they are willing to submit the files for official inclusion. If not, I can ask
one of my Japanese friends who uses latex whether he'd be willing to be the
maintainer.
On 08/03/2010 00:09, Wilfred van Rooijen wrote:
There are Japanese packages for polyglossia (the successor of babel
for xelatex) although at present polyglossia does not yet officially
support Japanese.
I looked at this again today, as I am currently helping the folks who
are preparing the
28 matches
Mail list logo
