Re: [XeTeX] Automatic glyph substitution

[Gareth Hughes]

On Fri, 2013-07-12 at 02:09 +0200, Zdenek Wagner wrote:
> Hi,
> 
> I have simila problem with old (commercial) fonts from Storm's
> Typokatalog. I have just extended the tex-text.map and it now
> contains:
> 
> ; TECkit mapping for TeX input conventions + Storm Typokatalog 4 fonts
> <-> Unicode characters
> 
> LHSName "TeX-storm4t"
> RHSName "UNICODE"
> 
> pass(Unicode)
> 
> ; ligatures from Knuth's original CMR fonts
> U+002D U+002D   <>  U+2013  ; -- -> en dash
> U+002D U+002D U+002D<>  U+2014  ; --- -> em dash
> 
> U+0027  <>  U+2019  ; ' -> right single quote
> U+0027 U+0027   <>  U+201D  ; '' -> right double quote
> U+0022   >  U+201D  ; " -> right double quote
> 
> U+0060  <>  U+2018  ; ` -> left single quote
> U+0060 U+0060   <>  U+201C  ; `` -> left double quote
> 
> U+0021 U+0060   <>  U+00A1  ; !` -> inverted exclam
> U+003F U+0060   <>  U+00BF  ; ?` -> inverted question
> 
> ; additions supported in T1 encoding
> U+002C U+002C   <>  U+201E  ; ,, -> DOUBLE LOW-9 QUOTATION MARK
> U+003C U+003C   <>  U+00AB  ; << -> LEFT POINTING GUILLEMET
> U+003E U+003E   <>  U+00BB  ; >> -> RIGHT POINTING GUILLEMET
> 
> ; additional ligatures for Štorm's fonts
> U+0066 U+0069   <>  U+FB01  ; fi
> U+0066 U+006C   <>  U+FB02  ; fl
> 
> I specify it as Mapping when loading the font.

Thanks for that. I have never been able to build TECkit on my Linux box
for some reason, so was hoping for another solution. However, I gave in
and built TECkit on a Windows VM. It made me think that it would be
useful to have an online library of mappings along with their compiled
files. Does anyone else on the list have any useful map files to
suggest?

Gareth.

> 
> 2013/7/12 Gareth Hughes :
> > Hi all!
> >
> > I am using Gill Sans MT for headings in a document that I'm setting. The
> > font I'm using does not automatically substitute the ligature glyphs
> > 'fi' and 'fl' that are supplied with the typefaces. Without editing the
> > font files, is there an easy way to make the substitution automatic
> > within the document? I know that I can use the \namedglyph command
> > sequence with xltxtra, but I am hoping for something more graceful.
> >
> > Thanks,
> >
> > Gareth.
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >   http://tug.org/mailman/listinfo/xetex
> 
> 
> 




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Automatic glyph substitution

[Gareth Hughes]

Hi all!

I am using Gill Sans MT for headings in a document that I'm setting. The
font I'm using does not automatically substitute the ligature glyphs
'fi' and 'fl' that are supplied with the typefaces. Without editing the
font files, is there an easy way to make the substitution automatic
within the document? I know that I can use the \namedglyph command
sequence with xltxtra, but I am hoping for something more graceful.

Thanks,

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

Thanks to all! I removed TeX Live and reinstalled. All is now working
fine. Clearly some yet undisclosed messiness happened when I tried
simply to install 2012 over 2011.

Thanks,

Gareth.

On Mon, 2012-07-09 at 15:03 +0200, Martin Schröder wrote:
> 2012/7/9 Ulrike Fischer :
> > I just saw that TexLive 2012 contains some instructions to
> > "upgrade". And while it is obviously not recommended to do it the
> > text contains a lot informations about possible sources of
> > "interference" problems:
> 
> "This procedure is not bullet-proof, or especially recommended;
> consider it provided as-is, to be used at your own risk." :-)
> 
> Best
>Martin
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

On Mon, 2012-07-09 at 10:06 +0200, Peter Dyballa wrote:
> Am 09.07.2012 um 04:04 schrieb Gareth Hughes:
> 
> > I thought fmtutil-local.cnf was just for customisation.
> 
> Indeed! And one customisation could have been to comment XeTeX related lines 
> copied from somewhere which made tlmgr remove or comment the lines in the 
> generated fmtutil.cnf.
> 
> I thought you would check the contents of 
> /usr/local/texlive/2011/texmf-var/web2c/fmtutil.cnf to see whether XeTeX 
> related formats are still mentioned there. One option is to simply run
> 
>   fmtutil-sys --listcfg
> 
> No sudo is necessary, it's a read-only process. You can compare the output 
> with that of
> 
>   fmtutil --listcfg

These files look identical to me, and both have xetex and xelatex.

> 
> When they're different, then you have private FMTs and you need to run
> 
>   fmtutil --byengine xetex
> 
> or a general
> 
>   fmtutil --refresh

Both of these fail and produce errors.
This is a summary of all `failed' messages:
`pdftex -ini  -jobname=eplain -progname=eplain
-translate-file=cp227.tcx *eplain.ini' failed
`pdftex -ini  -jobname=jadetex -progname=jadetex *jadetex.ini'
failed
`pdftex -ini  -jobname=pdfjadetex -progname=pdfjadetex
*pdfjadetex.ini' failed
`pdftex -ini  -jobname=latex -progname=latex
-translate-file=cp227.tcx *latex.ini' failed
`pdftex -ini  -jobname=pdflatex -progname=pdflatex
-translate-file=cp227.tcx *pdflatex.ini' failed
`pdftex -ini  -jobname=mllatex -progname=mllatex
-translate-file=cp227.tcx -mltex mllatex.ini' failed
`pdftex -ini  -jobname=pdftex -progname=pdftex
-translate-file=cp227.tcx *pdfetex.ini' failed
`pdftex -ini  -jobname=etex -progname=etex
-translate-file=cp227.tcx *etex.ini' failed
`pdftex -ini  -jobname=pdfetex -progname=pdfetex
-translate-file=cp227.tcx *pdfetex.ini' failed
`eptex -ini  -jobname=eptex -progname=eptex *eptex.ini' failed
`eptex -ini  -jobname=platex -progname=platex *platex.ini'
failed
`xetex -ini  -jobname=xetex -progname=xetex -etex xetex.ini'
failed
`xetex -ini  -jobname=xelatex -progname=xelatex -etex
xelatex.ini' failed
`pdftex -ini  -jobname=xmltex -progname=xmltex *xmltex.ini'
failed
`pdftex -ini  -jobname=pdfxmltex -progname=pdfxmltex
*pdfxmltex.ini' failed

However, no log file was written in ~/.texlive2012/texmf-var/web2c .
> 
> The options fmtutil or fmtutil-sys know can be found be found by running
> 
>   fmtutil --help
> 
> --
> Greetings
> 
>   Pete
> 
> I hope to die before I *have* to use Microsoft Word.
>   - Donald E. Knuth, 2001-10-02 in Tübingen
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

On Mon, 2012-07-09 at 11:50 +0200, Ulrike Fischer wrote:
> Am Mon, 9 Jul 2012 01:02:45 +0100 schrieb Gareth Hughes:
> 
>  
> > Checking the path with "which xelatex" gives
> > "/usr/local/texlive/2011/bin/x86_64-linux/xelatex", which is correct.
> 
> Didn't you wrote you updated to TeXLive 2012? Then why do you get a
> 2011 path?
> 

Ulrike, I think this is normal. The first install on this computer was
2011. When previously I've updated extant installations, I noted that
the year number of the directory doesn't change. I suppose I could just
rip the whole thing out and fresh install, but it's not always easy to
know whether one has taken out the entire old installation.

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

Yes, all these work, and the files are in the correct place.

Gareth.

On Mon, 2012-07-09 at 10:12 +0200, Zdenek Wagner wrote:
> 2012/7/9 Peter Dyballa :
> >
> > Am 09.07.2012 um 04:04 schrieb Gareth Hughes:
> >
> Start with the basic commands:
> which xetex
> which fmtutil-sys
> which kpsewhich
> 
> If it finds your TeX Live binaries, try
> 
> kpsewhich fmtutil.cnf
> 
> >> I thought fmtutil-local.cnf was just for customisation.
> >
> > Indeed! And one customisation could have been to comment XeTeX related 
> > lines copied from somewhere which made tlmgr remove or comment the lines in 
> > the generated fmtutil.cnf.
> >
> > I thought you would check the contents of 
> > /usr/local/texlive/2011/texmf-var/web2c/fmtutil.cnf to see whether XeTeX 
> > related formats are still mentioned there. One option is to simply run
> >
> > fmtutil-sys --listcfg
> >
> > No sudo is necessary, it's a read-only process. You can compare the output 
> > with that of
> >
> > fmtutil --listcfg
> >
> > When they're different, then you have private FMTs and you need to run
> >
> > fmtutil --byengine xetex
> >
> > or a general
> >
> > fmtutil --refresh
> >
> > The options fmtutil or fmtutil-sys know can be found be found by running
> >
> > fmtutil --help
> >
> > --
> > Greetings
> >
> >   Pete
> >
> > I hope to die before I *have* to use Microsoft Word.
> > - Donald E. Knuth, 2001-10-02 in Tübingen
> >
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >   http://tug.org/mailman/listinfo/xetex
> 
> 
> 




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

Yes, sudo fmtutil-sys produces the same error.

fmtutil.cnf exists under texmf-var/web2c, but there are no files in
texmf-local/web2c. I thought fmtutil-local.cnf was just for
customisation.

Gareth.

On Mon, 2012-07-09 at 02:22 +0200, Peter Dyballa wrote:
> Am 09.07.2012 um 02:02 schrieb Gareth Hughes:
> 
> > So, still not working; I'm sure I'm just overlooking something. Any
> > other suggestions are welcome.
> 
> Check if it exists: /usr/local/texlive/texmf-local/web2c/fmtutil-local.cnf. 
> It is used by tlmgr to generate the proper CNF file: 
> /usr/local/texlive/2011/texmf-var/web2c/fmtutil.cnf.
> 
> With sudo you have to use fmtutil-sys.
> Without sudo you have to use fmtutil.
> 
> -- 
> Greetings
> 
>   Pete
> 
>(This space left blank for technical reasons.)
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

Thank you all.

"fmtutil --refresh --byengine xetex" fails. It also fails if I try it
from tlmgr. I'm not sure if it's meaningful, but when this command is
run with sudo, it gives the error "fmtutil: no format depends on engine
`xetex'."

Checking the path with "which xelatex" gives
"/usr/local/texlive/2011/bin/x86_64-linux/xelatex", which is correct.

So, still not working; I'm sure I'm just overlooking something. Any
other suggestions are welcome.

Thanks,

Gareth.

On Mon, 2012-07-09 at 00:45 +0200, Peter Dyballa wrote:
> Am 08.07.2012 um 20:54 schrieb Martin Schröder:
> 
> > fmtutil --refresh --byengine xetex
> 
> Shouldn't it be 'sudo fmtutil-sys --refresh --byengine xetex'?
> 
> --
> Mit friedvollen Grüßen
> 
>   Pete
> 
> Wer nichts zu verbergen hat, hat schon alles verloren.
>   (Juli Zeh)
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] xelatex.fmt doesn't match xetex.pool

[Gareth Hughes]

Hi!

I just updated to TeX Live 2012 on Ubuntu, but XeLaTeX now fails with
the message "xelatex.fmt doesn't match xetex.pool". I'm sure there's an
easy way of fixing this. Ang suggestions?

Thanks,

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] New font from Brill

[Gareth Hughes]

On Fri, 2012-02-03 at 12:14 +0100, Zdenek Wagner wrote:
> 2012/2/3 Gareth Hughes :
> > ... and is distributed gratis.
> > http://www.brill.nl/news/brill-typeface
> >
> Unfortunatelly it is not free, it cannot be redistributed and can only
> be used for noncommercial works, thus I cannot use it to typeset a
> book.

That's why I used the word 'gratis' rather than 'free', implying free of
cost but under a restrictive licence. I still think the font is
interesting and useful: I produce a lot of noncommercial typesetting.

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] New font from Brill

[Gareth Hughes]

The academic publisher Brill has developed a new LCG font with lots of
glyphs that will be of interest to those who need lots of diacritics and
various other signs. Brill boasts that it can be used for any
orthography in Latin (including IPA), Cyrillic or Greek. The font was
designed by John Hudson of Tiro Typeworks, and is distributed gratis.
http://www.brill.nl/news/brill-typeface

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Current Hebrew month spelled incorrectly in Polyglossia

[Gareth Hughes]

It would be good to have the option to choose מרחשון, as that's what I
would normally write. Could we have a 'marcheshvan' option for
choosing this more traditional spelling?

Thanks,

Gareth.

On 23 November 2011 17:41, Joel C. Salomon  wrote:
> On 11/23/2011 01:41 AM, Ari Meir Brodsky wrote:
>> The current Hebrew month is spelled incorrectly when using
>> \texthebrew{\today} in Polyglossia.  It seems that the error is in line 58
>> of hebrewcal.sty, where the name השון should be changed to חשון.
>
> Is there an option to use the full name מרחשון?
>
> —Joel
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>



-- 
Gareth Hughes
garzoh...@gmail.com
public key ID: 0x9F32AF1E



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Polyglossia/makecmds: Old document fails to compile

[Gareth Hughes]

On Fri, 2011-09-30 at 12:44 +0200, Susan Dittmar wrote:
> Dear Gareth,
> 
> this one should be easy to fix. It's a known bug / inconsistency with
> polyglossia. Add
> 
> \usepackage{xkeyval}
> 
> in a line before the call to polyglossia.
> 
> Hope that helps,
> 
>   Susan

Dear Susan,

That's perfect, and it shows me for taking my eye of XeTeX issues for a
little while!

Thank you,

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Polyglossia/makecmds: Old document fails to compile

[Gareth Hughes]

Dear all,

I'm sure there's an easy answer to this, but it's always frustrating
when old documents suddenly do not compile any more. I'm writing a
fairly straightforward academic article with the first three lines


> \documentclass[headsepline]{scrartcl}
> \usepackage{fontspec, polyglossia, xcolor, soul, makeidx, hyperref}
> \usepackage[english=british]{csquotes}

When I compile the document, it stops with the message


> (/usr/local/texlive/2011/texmf-dist/tex/latex/makecmds/makecmds.sty)
> ! Undefined control sequence.
> l.402 \define@boolkey
>  {polyglossia}[xpg@]{localmarks}[false]{%

Any thoughts on how to overcome this and get the document to compile?

Thanks,

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Critical edition of an Arabic poem with ednote and bidipoem.sty

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/08/11 16:06, Christopher Braun wrote:
> Dear list members,
> 
> for a critical edition of an Arabic text including poetry I would like
> to use bidipoem, but my ednote commands to edit the apparatus criticus
> do not work in the traditionalpoem-environment. Is there a solution to
> this problem? Moreover, it is not possible to add marginnotes and the
> linenumbering is interrupted.
> 
> Thank you for your help!
> 
> Best wishes,
> 
> Christopher  


Dear Christopher,

Ednote and bidipoem conflict because their environments do similar
things with text layout. There are workarounds, but you have to choose
which package to work with, and then work in features from the other. My
xesyriac package (http://users.ox.ac.uk/~wolf2305/xesyriac.html, which
still needs a bit of work) sets Syriac poetry using the traditionalpoem
environment and adds line numbers. It also can add dramatic personae to
dialogue poems. Feel free to use any bits of it that meet your needs.
There's plenty of scope for development of packages that handle this
kind of thing in XeLaTeX. I'm sure Vafa and others will have some
thoughts on the best way to proceed.

Best wishes,

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOU9Kk9UDttp8yrx4RAj/BAKCiOAca3v85zuRtmMYtO8yLdLnPAgCglcHC
5RizlQ/eRzQfCf3MXiadAog=
=U1HE
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Graphics with XeLaTeX and bclogo

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/08/11 00:24, Vafa Khalighi wrote:
> Add this code to preamble of your document and it compiles fine:
> 
> \makeatletter
> 
> \@namedef{Gin@rule@.mps}#1{{eps}{.mps}{#1}}
> 
> \def\Gin@extensions{.pdf,.eps,.ps,%
> 
> .png,.jpg,.bmp,.pict,.tif,.psd,.mac,.sga,.tga,.gif,.mps}
> 
> \makeatother
> 
> 
> (To the maintainers of xetex.def): this can go in xetex.def

Thanks, وفا. This does the trick. I've actually made a local copy of
bclogo.sty with this definition in an \ifxetex ... \fi. I think I shall
send the package maintainers notification, as I wonder whether this
allowance be better in the package rather than in xetex.def. However,
there is the problem then of forcing all users of bclogo.sty to use
ifxetex.sty.

Thanks,

Gareth.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOOots9UDttp8yrx4RAv16AJwKVdpa4OOWNUa+2Uk9FfRw+EOzlQCgjf/T
VsdCNR99zJS1l9C0dNRBRxM=
=U/ZB
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Graphics with XeLaTeX and bclogo

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear XeTeXnicians,

Is there a decent guide anywhere to handling graphics with XeLaTeX? I've
ploughed through the TikZ & PGF manual, and confess that handling
graphics is not something I'm used to. I'm particularly interested in
using the bclogo to create a document I'm working on, but the logo part
of it, from a Metapost file, doesn't display. I thought that this might
have been because the bclogo package doesn't take XeTeX into account,
whereas it clearly thinks about PDFTeX, but that doesn't seem to be the
case. Has anyone used bclogo under XeLaTeX successfully?

Thanks,

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOOciM9UDttp8yrx4RAhBnAKCVhr1qq2UQSo9g2MP+2fJTn5bzAQCeI1/B
hxjBCh/zpMTjSmCEf5x12Wc=
=yX4m
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xparse fails

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/08/11 01:31, Herbert Schulz wrote:
>> 
>> Did you do the update using
>> 
>> tlmgr update --all
>> 
>> (prefixed by sudo if necessary on your system)? It appears that the
>> experimental packages were re-organized and some were deleted and
>> others added on my system today.
>> 
>> Good Luck,
>> 
>> Herb Schulz (herbs at wideopenwest dot com)
> 
> 
> Howdy,
> 
> PPS: the xpackages folder is empty on my system.
> 
> Good Luck,
> 
> Herb Schulz (herbs at wideopenwest dot com)

Ah, that's it. Of course, I usually just update the packages in the
update list. As soon as I used "update all" it deleted the everything in
l3packages. The version I thought was out-of-date is now used! Thanks, Herb.

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFON1Fi9UDttp8yrx4RAnpeAJsFelj8Y520wYqFzzLw7p86u+lHYQCglyCI
u33pDbXUZpgX98BbxL5hJGA=
=13Gl
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xparse fails

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/08/11 23:35, Vafa Khalighi wrote:
> There was a similar problem reported a while ago. I do not know about
> xparse internals as I do not maintain it but Joseph should know what is
> going on. See also the similar issue which was reported in July:
> 
> http://tug.org/pipermail/xetex/2011-July/020840.html

Now that's interesting. My system actually seems to have two copies of
xparse.sty on it. The paths and ids of each are

texmf-dist/tex/latex/l3packages/xparse/xparse.sty (Id: xparse.dtx 2492
2011-07-02 13:40:38Z joseph)
texmf-dist/tex/latex/xpackages/xbase/xparse.sty (Id: xparse.dtx 2219
2011-04-08 21:07:45Z joseph)

However, the command "kpsewhich xparse.sty" only delivers the first of
these (isn't it supposed to deliver all occurrences?). The line that
caused problems in that old thread is corrected in the newer copy (first
copy), but not in the older one.

The thing is that it has only just stopped working now. So, a recent
update has created the problem.

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFONzv59UDttp8yrx4RAlBJAJ4mioDZQ3ivNU1SRxKq7lz/W/13VACeP+a8
MMCP/+rG5yxSOLC91akQZsU=
=1gQj
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xparse fails

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/08/11 23:52, Herbert Schulz wrote:
> 
> Howdy,
> 
> What platform are you using? You seem to be using a xetex from TL-2011 but 
> the xparse is coming form a TL-2009 distribution.
> 
> Good Luck,
> 
> Herb Schulz
> (herbs at wideopenwest dot com)

No, that reference to 2009 is simply the name of the directory. My
initial installation of TeX Live was the 2009 version. The directory
name is still 2009, but the installation, by TeX Live Manager, is an
up-to-date TeX Live 2011. Perhaps it is too up-to-date! My xparse
documentation says that it was released 2011/07/02.

Gareth.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFONzfS9UDttp8yrx4RAoAGAJ9Md6NK/4EiuCUV3W4HaXfIWqjJrACgktPx
1TbV+rIynNrJYc3TJrFYb40=
=5RvE
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] xparse fails

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear fellow XeTeXnicians,

TeX Live updated a couple of times over the weekend, and a document that
compiled fine on Friday now fails. The document is not complex, and now
I see almost everything I've written is uncompilable. These documents
use fontspec, polyglossia, soul and hyperref, but I believe that it's
the fontspec call on xparse that creates the problem. Somewhere
something has changed.

The error message is
> (/opt/texlive/2009/texmf-dist/tex/latex/l3packages/xparse/xparse.sty 
> ! Undefined control sequence.  \ExplFileName
> 
> l.57 ...e}{\ExplFileVersion}{\ExplFileDescription}

My XeTeX version is
> This is XeTeX, Version 3.1415926-2.3-0.9997.5 (TeX Live 2011)
> (format=xelatex 2011.7.20)  1 AUG 2011 23:18

The TLM tells me that I'm using revision 22347 (ver. SVN 2321) of xpackages.

Is anyone else experiencing problems? Can anyone sort this out for me?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFONyjO9UDttp8yrx4RAvKEAJ9lyvjXhxddOeEgjmLWG4RgOXHogwCeIL0P
rveyCdOh6miiWrV6AkDtC44=
=UDPG
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem Problem

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/06/11 09:23, Heba Soliman wrote:
> Dear All:
> 
> I am typsetting a file with traditional poem and I have a problem that a
> "traditionalpoem" within "footnote within traditionalpoem" doesn't work.
> So, I will appreciate if anyone tells me how to solve this issue.
> 
> 
> %%
> 
> \documentclass{amsbook}
> 
> \usepackage[T1]{fontenc}
> \usepackage[silent,quiet,no-math]{fontspec}
> \usepackage{bidi}
> \usepackage{bidipoem}
> 
> \setmainfont{YakoutLinotypeLight-Regular.ttf}
> 
> \setRL
> \rightfootnoterule
> 
> \begin{document}
> 
> \begin{traditionalpoem}
>   أبا الهول، ماذا وراءَ البقا & ءِ — إذا ما تطاول — غيرُ
> الضجَر؟\footnote{\begin{traditionalpoem}
> سئمت تكاليف الحياة ومَنْ يَعِش&ثمانين حَوْلاً لا أبا لك يسأم
> \end{traditionalpoem}}
>  \end{traditionalpoem}
>  \end{document}
> 
> %%
> 
> 
> Thanks,
> 
> Heba

Dear Heba,

Have you tried using \footnotemark and \footnotetext to deal with
footnotes within this environment? I think that's what I've used for
textual variants in poems. I wouldn't wonder that the traditionalpoem
environment will not work in a footnote anyway. I've never tried setting
whole lines in the footnotes, just short-phrase variants.

Best wishes,

Gareth.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOAIJ/9UDttp8yrx4RAgfDAKC1pCPbk9NPmO6ImFlt9dgc9y8kJgCfVKde
NS+31HpvRHRIWzBGfESBVwI=
=a+uH
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [Off-topic] Persian versus Farsi

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've been learning Middle Persian or Pahlavi (never Middle Farsi or
Fahlabi!). The language is called Pārsīg (p'lsyk) at that period. The
adoption of the spelling with F is an arabicisation during the Islamic
period. Then, Arabic became the prestige language of Persia due to its
religious and political dominance. Arabic has no P (you can drink Bibsi
if you don't drink Kuka Kula), so the Arabic name of the language is
Fārsī, and this spelling and pronunciation became standard in Persian
(as noted by the 'Fârsi' in the title of the academy). However, the
spelling and pronunciation Pârsi is sometimes used, often as a conscious
de-arabicisation, and always (?) by Zoroastrians. Some in the Persian
diaspora, particularly after the revolution, popularised the use of
'Farsi' as the name of the language internationally, but linguists, both
within and without Iran, continue to use 'Persian' as the English name
of the language at all stages of its history. Using 'Farsi' in English
is a bit like talking about 'Français' or, as Vafa mentioned, 'Türkçe'
(note spelling). As you can see, politics is a major determinant on
language naming.

Gareth.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFN81aq9UDttp8yrx4RAulLAJ9hhazenLZl7qjP2LNxEKtYpcjZ3QCeNGCt
vmgklB1OccqNOj9XQLF/4Gk=
=N5ht
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [Off-topic] Persian versus Farsi

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've been learning Middle Persian or Pahlavi (never Middle Farsi or
Fahlabi!). The language is called Pārsīg (p'lsyk) at that period. The
adoption of the spelling with F is an arabicisation during the Islamic
period. Then, Arabic became the prestige language of Persia due to its
religious and political dominance. Arabic has no P (you can drink Bibsi
if you don't drink Kuka Kula), so the Arabic name of the language is
Fārsī, and this spelling and pronunciation became standard in Persian
(as noted by the 'Fârsi' in the title of the academy). However, the
spelling and pronunciation Pârsi is sometimes used, often as a conscious
de-arabicisation, and always (?) by Zoroastrians. Some in the Persian
diaspora, particularly after the revolution, popularised the use of
'Farsi' as the name of the language internationally, but linguists, both
within and without Iran, continue to use 'Persian' as the English name
of the language at all stages of its history. Using 'Farsi' in English
is a bit like talking about 'Français' or, as Vafa mentioned, 'Türkçe'
(note spelling). As you can see, politics is a major determinant on
language naming.

Gareth.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFN81bF9UDttp8yrx4RAuhdAJ9jb5CsYLQsiz7OjrJ0ZzoV3KXDXwCfQ+6q
MoW1wfmTgrg2MBpWhPAfAwU=
=qbvT
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Mongolian

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/06/11 09:53, Жаргал Бадагаров wrote:
> Hello members,
> 
> 
> My name is Jargal. I am interested in the Mongolian Vertical Script Support 
> in MacOS. I have found a 2005 presentation of XETEX made in Uhan, where it is 
> said that Mongolian had not yet obtained a full support of all its features.
> 
> Do you know if it has been being developed so far? Any advancements for the 
> Mongolian Script Support? Any information would be highly appreciated as I am 
> quite a newbee in the field of unix/linux and macos,
> 
> Thank you and have a good day!
> 
> Jargal Badagarov
> 

Dear Jargal,

Welcome! I know absolutely no Mongolian, but I made decorative use of
the vertical script in a poster for a seminar I gave on a couple of
13th-century Öngüt monks. The PDF can be seen at
http://www.garzo.co.uk/documents/poster.pdf. I've attached the source
file. As you can see, I've used Code2000, which is not a specialist
Mongolian font, but does the trick (I hope!). The XeTeX manual has
instructions for writing vertical Chinese, which can be followed. As you
can see \rotatebox{-90} is used to turn the text to vertical. I hope
that helps a little. Maybe someday I shall learn some beautiful Mongolian!

Best wishes,

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFN67Ew9UDttp8yrx4RAjBpAKCVH7d3BRb4mnoE2yn1ZRH3QjTq1ACgp957
TooHrEn35OejTn1t674a5J8=
=DWF1
-END PGP SIGNATURE-
\documentclass[a4paper, 12pt]{scrartcl}
\usepackage{xltxtra, polyglossia, lettrine}
\setmainlanguage[variant=british]{english}
\setotherlanguage{syriac}
\defaultfontfeatures{Mapping=tex-text}
\setmainfont[
	Numbers=OldStyle,
	Ligatures=Historical,
	ItalicFeatures={
		Variant=2,
		Style=Alternate},
	Fractions=On]
	{Linux Libertine O}
\setsansfont[
	BoldFont={Museo 700},
	Ligatures=Discretionary,
	Numbers=OldStyle]
	{Museo 500}

\newfontfamily\syriacfont[Script=Syriac, Scale=MatchLowercase]{East Syriac Adiabene}
\newfontface\phagspaseal[Script=Phags-pa, Scale=0.7]{BabelStone Phags-pa Seal}
\newfontface\phagspabook[Script=Phags-pa, Scale=0.7]{BabelStone Phags-pa Book}
\newfontface\bicig[Script=Mongolian]{Code2000}

\title{\vspace{-9pt}The Monks of Kublai Khan\\
	\Large From Beijing to Baghdad and Beyond}
\author{Gareth Hughes}
\date{19:30 Tuesday 19\textsuperscript{th} May 2009\\Haldane Room, Wolfson College}
\subject{\vspace{-4em}Wolfson College Research Fellows' Seminar\\[10pt]
\textsyriac{ܥܲܠ ܬܲܫܥܝܼܬ݂ܵܐ ܕ݂ܡܵܪܝ ܝܲܗ̣݇ܒ݂ܐܲܠܵܗܵܐ ܘܲܕ݂ܪܲܒ݁ܲܢ ܨܵܘܡܵܐ܀}\\[5pt]
\raisebox{110pt}{%
	\rotatebox{-90}{\phagspaseal ꡘꡎꡎꡬ ꡛꡝꡟꡏ}
	\rotatebox{-90}{\phagspabook ꡘꡎꡎꡬ ꡛꡝꡟꡏ}
	\rotatebox{-90}{\bicig\huge ᠷᠠᠪᠪᠠᠨ ᠰᠠᠸᠮᠠ}}
\includegraphics[scale=0.1]{Museum_für_Indische_Kunst_Dahlem_Berlin_Mai_2006_066.jpg}
\raisebox{110pt}{%
	\rotatebox{-90}{\bicig\huge ᠮᠠᠷ ᠶᠠᠪᠠᠯᠠᠾᠠ}
	\rotatebox{-90}{\phagspabook ꡏꡘ ꡗꡎꡙꡜ}
	\rotatebox{-90}{\phagspaseal ꡏꡘ ꡗꡎꡙꡜ}}}
	
\pagestyle{empty}
\renewcommand*{\titlepagestyle}{empty}

\usepackage[xetex, colorlinks, pdfdisplaydoctitle,
	pdfauthor={Gareth Hughes},
	pdftitle={The Monks of Kublai Khan: From Beijing to Baghdad and Beyond},
	pdfsubject={Wolfson College Research Fellows' Seminar},
	pdfkeywords={},
	pdfcreator={XeLaTeX with the Fontspec, Polyglossia, Lettrine and Hyperref packages}]{hyperref}
	
\begin{document}
\maketitle

\vspace{-1em}\lettrine{\textcolor{red}{I}}{n the second half of the 13\raisebox{2pt}{\scriptsize th} century}, two Christian monks of the Öngüt tribe of Inner Mongolia set out from Beijing to make pilgrimage to Jerusalem. The Beijing from which they began their journey was known to them as Khanbalïq, the capital of Kublai Khan, Mongol Great Khan (1260--94), grandson of Genghis Khan, founder of the Yuan dynasty of China and suzerain of territory spread as far as Turkey in the west.

Near contemporaries of Marco Polo, yet reversed, the story of Ṣāumā and Marqos, preserved in Syriac, takes us from Beijing, through the steppe of their tribal homeland in Inner Mongolia, along the Silk Road, winding around deserts and through mountain passes, and into the Central Asian 'Stans, Iran and Iraq.

Ṣāumā and Marqos were monks of the Church of the East, governed by its Catholicos-Patriarch in Baghdad. Their Christianity was a truly Asian one, untouched by European `Christendom'. A church that had followers in India, South-East and Central Asia, China, Siberia, Afghanistan, Iran and Iraq. A church that is dubbed `Nestorian', an ancient heresy, by the European churches of Rome and Constantinople. Although the majority of Öngüt were Christian, others practised Buddhism, Manichæism or Shamanism.

Politics, of both church and state, prevented the monks from a

Re: [XeTeX] error \begin{document}

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/06/11 18:57, Ruth Robbins wrote:
> just tried desperate measures--trashed the aux files and then ran the
> typesetting again and it worked.  So something must have been wrong with
> an aux file.
> Ruth

Hi Ruth!

Deleting the aux file before recompiling when it fails for no reason is
just one of those tricks that I've picked up on the way. Often processes
are two-stage. If you make an error that makes the compile fail, it can
be written to the aux file, and ensure that, even if the original error
is fixed, it keeps failing. I thought I'd comment just to keep the
record for the future perturbed!

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFN6AaY9UDttp8yrx4RArPpAKCMAkUC8kJnbDyUdkTUSOK3Ah6iBgCeO/3j
5hKgKzp2aPoWyzy95aM0lzw=
=kCm/
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Coptic typesetting backwards with polyglossia

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/04/11 01:31, Jonathan Harmon wrote:
> I was so pleased that the polyglossia package started supporting more
> languages, including Coptic. But when I try to invoke it with
> \textcoptic{} or the coptic environment, it typesets right-to-left, i.e.
> backwards. Interestingly, the problem doesn't seem to exist
> if \textcoptic{} is not invoked. Is there a reason for this, or was
> there a step I missed?
> 
> Here is the text of the example file:
> 
> \documentclass{article}
> \usepackage{fontspec,xunicode,xltxtra}
> 
> \usepackage{polyglossia}
> 
> \setmainlanguage{english}
> 
> \setotherlanguage{coptic}
> 
> \setmainfont{Antinoou}
> 
> \newfontfamily\copticfont{Antinoou}
> 
> \begin{document}
> 
> Here is some English text.
> 
> \bigskip
> 
> And now for the Coptic:
> 
> ⲛⲁⲉⲓ ⲛⲉ ⲛ̅ϣⲁϫⲉ ⲉⲑⲏⲡ ⲉⲛⲧ-ⲁ-ⲓ̅ⲥ̅
> 
> \textcoptic{ⲛⲁⲉⲓ ⲛⲉ ⲛ̅ϣⲁϫⲉ ⲉⲑⲏⲡ ⲉⲛⲧ-ⲁ-ⲓ̅ⲥ̅}
> 
> \begin{coptic}
> 
> ⲛⲁⲉⲓ ⲛⲉ ⲛ̅ϣⲁϫⲉ ⲉⲑⲏⲡ ⲉⲛⲧ-ⲁ-ⲓ̅ⲥ̅
> 
> \end{coptic}
> 
> \end{document}

The problem is in the file
TEXMF/tex/xelatex/polyglossia/gloss-coptic.ldf which says

> \PolyglossiaSetup{coptic}{
>   script=Coptic,
>   direction=RL,
>   scripttag=copt,
>   langtag=COP,
>   hyphennames={coptic},
>   hyphenmins={2,2},
>   fontsetup=true
> }

If that's changed to direction=LR, Coptic should work properly.

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNlen/9UDttp8yrx4RAnymAJ9VgHzIPsv5VeeV0xed2dNsWCMAoQCgoPGD
mjVFcHmxRO3tPYi8jLPU2rc=
=ei+K
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Xelatex, kannada, sanskrit and ligatures

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 26/02/11 06:39, Harish Gopala wrote:
> Hello,
> 
> I have the problem with Xelatex. When I compile the below file using
> xelatex, it complains a little while compiling, but the ligatures are
> all wrong in the output pdf file.

Saying that the ligatures are all wrong isn't too helpful. Do you mean
that the ligatures are not forming (likely) or that the wrong ligatures
are forming (less likely).

Please help. The source is as below:
> --
> \documentclass[12pt]{article}
> \usepackage{fontspec}
> \newfontfamily{\Kannada}{Tunga}
> \newfontfamily{\Devanagari}{CDAC-GISTSurekh}

Without seeing the output or knowing the fonts, it is likely that you
have to turn script features on in fontspec. Try rewriting the font
calls with

\newfontfamily{\Kannada}[Script=Kannada]{Tunga}
\newfontfamily{\Devanagari}[Script=Devanagari]{CDAC-GISTSurekh}

Hope that helps,

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNaORj9UDttp8yrx4RAm3HAKCvmj/TO1/JbOW3898E3Kt+fw3qYgCfTIWR
LNAWc9w4pWBUPZjiRWXq3pc=
=0v5b
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] XeSyriac: Syriac typesetting for XeLaTeX: alaph-test version

[Gareth Hughes]

The support for Aramaic numerals isn't really working yet, but has been
half written into xesyriac.sty. Thus, line 243 might cause problems, so
please comment it out if processing fails. It's probably easier to do
that for me to upload the font files for some code that doesn't work or
to cut the code out. I hope this is a temporary glitch, and I'll let the
list know when I've updated the code.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] XeSyriac: Syriac typesetting for XeLaTeX: alaph-test version

[Gareth Hughes]

Tentatively, I offer the alaph-test version of XeSyriac, a package for
Syriac typesetting with XeLaTeX. I've set up a web page for the package
from which all or parts of it may be downloaded:
http://www.garzo.co.uk/xesyriac

There is still quite a lot of work that I intend to do on the package,
and that is clear from the documentation. However, I realised it would
help me to bring the monster out into the open and seek advice on its
development. I am not technically minded, and have developed this
package as an a regular end user. With this in mind, I would like some
feedback from

1. The handful of Syriacists who now use XeLaTeX, to ascertain if this
is what we want/need, and if there are any end-user requests.

2. Those who know what packages should look like and how to code them,
to correct my errors and over-exuberances.

I am already grateful to those who have suggested snippets of code here
and there that have gone into the package. I have tried to recognise
each of you, and will continue to do so for all who offer further guidance.

With the fear and trepidation of a new parent,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Polyglossia/Split Hebrew footnote between pages

[Gareth Hughes]

sjo wrote:
> I am writing an English document using \begin{hebrew} to insert Hebrew
> text where necessary. Sometimes I have an English paragraph with a
> footnote that is a long piece of Hebrew text. So I use a macro such
> as:
> 
> \usepackage{polyglossia} ...
> 
> \def\hfootnote#1{\footnote{\RL{\hebrewfont #1}}}
> 
> to insert the Hebrew footnote (I tried a variety of approaches
> including \texthebrew{} in a \footnote, but ran into a variety of
> problems).
> 
> The above macro works well, except that it does not split footnotes to
> the next page thus creating short pages that do not look good. It
> keeps the whole footnote on one page.
> 
> Any suggestions would be very much appreciated.
> 
> Jon

Hi Jon!

Can you not use bidi's \RTLfootnote command? You're already loading bidi
in the background if you're loading polyglossia to write Hebrew. Then
you could write something like

\def\hfootnote#1{\RTLfootnote{\hebrewfont #1}}

Any good?

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] hyphenation in Ethiopian languages

[Gareth Hughes]

Dear Adam,

Line 7 of gloss-amharic.ldf in the polyglossia package has

  hyphennames={amharic,nohyphenation},

which I take to mean that you'll get no hyphenation wherever 'amharic'
is active. The next line is commented out

  %hyphenmins={2,2},

so I presume that some rules were intended (François?). If the rules are
that hyphenation can occur anywhere, I'm sure this would be fairly
easily to implement.

Gareth.

Adam McCollum wrote:
> Dear list members,
> 
> I've recently drawn up a short document in Ge`ez (classical Ethiopic) using
> Polyglossia and I see that the hyphenation is wrong. As some of you know,
> languages that use the Ethiopic script, including Ge`ez and Amharic, place a
> word divider—it looks somewhat like a thick colon—between each word and two
> of these dividers side by side between sentences; see some Amharic examples
> here<http://books.google.com/books?id=r87yh5z66TEC&printsec=frontcover&dq=amharic&hl=en&ei=U7TSTIX-Ds2r8AaT6LxF&sa=X&oi=book_result&ct=book-thumbnail&resnum=6&ved=0CEwQ6wEwBQ#v=onepage&q&f=false>.
> That being the case, a word may be broken at any syllable (the script is a
> syllabary, not an alphabet) at the end of a line, but there is nothing
> corresponding to a hyphen. An additional matter of importance is that no
> line should begin with the single or double word divider. How should this be
> fixed?
> 
> Here is a minimal example:
> 
> \documentclass[12pt]{article}
> 
> \usepackage{fontspec}
> \usepackage{polyglossia}
> 
> \setmainlanguage{english}
> \setotherlanguage{amharic}
> 
> \newfontfamily\amharicfont[Script = Ethiopic, Scale = 1.3]{Abyssinica SIL}
> 
> \begin{document}
> 
> \title{Sample in Gǝ`ǝz}
> \maketitle
> 
> \begin{amharic}
> እስመ ፡ አግዚአብሔር ፡ አምላክ ፡ ማእምር ፡ ውእቱ ። እግዚአብሔር ፡ አስተደወ ፡ መንብሮ ። ወአድከመ ፡ ቅሥተ ፡
> ኀያላን ። ወአቅነቶሙ ፡ ኀይለ ፡ ለድኩማን ። ጽጉማን ፡ እክል ፡ ርኅቡ ። ወርኁባን ፡ ጸግቡ ። እስመ ፡ መካን ፡
> ወለደት ፡ ሰብዐተ ፡ ወወለድሰ ፡ ስእነት ፡ ወሊደ ፡ እግዚአብሔር ፡ ይቀትል ፡ ወየሐዩ ። ያወርድኒ ፡ ውስተ ፡ ሲእል
> ፡ ወየዐርግ ። እግዚአብሔር ፡ ያነዲ ፡ ወያብዕል ። ያኀስርሂ ፡ ወያከብር ፡ ዘያነሥኦ ፡ እምድር ፡ ለነዳይ ። ከመ ፡
> ያንብሮ ፡ ምስለ ፡ ዓበይ[ተ] ።
> \end{amharic}
> 
> \end{document}
> 
> With many thanks in advance for the help,
> 
> Adam McCollum, Ph.D.
> Lead Cataloger, Eastern Christian Manuscripts
> Hill Museum & Manuscript Library
> Saint John's University
> P.O. Box 7300
> Collegeville, MN 56321
> 
> (320) 363-2075 (phone)
> (320) 363-3222 (fax)
> www.hmml.org
> 
> 
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] (Xe)LaTeX output in a non-(Xe)LaTeX scholarly community

[Gareth Hughes]

On the matter of declining skills in typesetting I'm reminded of an
Oxford apocryphon of a printer who was preparing a Sanskrit grammar. The
printer contacted the author, an esteemed professor, with a crucial
error in the Sanskrit text. The professor first felt angry at being
questioned on matters of Sanskrit by a printer, but verified the
reported the error in his own copy. Returning to the printer he asked
how he'd managed to spot the error. The printer replied that, after
setting pages and pages in a script he could not read, he had learnt
that one of them never follows one of them! Ah... attention to detail;
they don't make them like that anymore!

Gareth.

John Was wrote:
> Well I'm still in the Press once a week at least (for choir practice!)
> so I shall make sure these comments reach the right ears.  They
> correspond, unfortunately to my own impression.  Leofranc
> Holford-Strevens works heroically on critical editions but he is the
> sole in-house editor left and can't possibly handle them all.  I think
> he is pretty well full-time on large projects with extensive commentary
> (and still finds time to publish and lecture extensively on an
> astonishing range of topics).
> 
> Getting back to TeX-related matters, the hyphenation patterns available
> in XeTeX (even to 'plain' users like myself) are an enormous help, even
> if I disagree with the English at frequent points (the Latin rarely lets
> me down, aside from a few rogues - is hucusque one? - which I guess are
> analagous to Knuth's 'manuscript' in refusing to comply with the
> algorithms).  No one bothers to read people like Priscian on what should
> be done with Greek and Latin, and no one at OUP involved in passing
> proofs would have the faintest idea about this subject.  Neither, alas,
> do authors - with the Dictionary of Medieval Latin (which I have just
> relinquished with completion of Fascicule XIII in the middle of letter
> 'R') it was left entirely to me, and I fear that laxity in this matter
> will pervade future fascicules as it did in some of those that preceded
> my involvement.  When I asked the compilers  to keep a look-out for any
> bad hyphenations that I might have missed in perusing and correcting the
> proofs, they asked me to explain the rules!
> 
> John
> 
> 
> 
> - Original Message - From: 
> To: 
> Sent: 23 October 2010 15:05
> Subject: Re: [XeTeX] (Xe)LaTeX output in a non-(Xe)LaTeX scholarly
> community
> 
> 
>> Yes, as you would guess, the copy-editor marked up my files by hand
>> and sent me the hard copy.
>>
>> Recent OUP critical editions in Greek prose could use a lot more
>> copy-editing; I would assert that their production standards in this
>> area have fallen drastically in the last decade. We have new editions
>> of the Greek orators Demosthenes and Lysias in the Oxford Classical
>> Text series, all filled with rampant flaws in hyphenation and line
>> numbering in the apparatus. Reviews have also identified numerous
>> slips of a more substantial nature, that seem to suggest very little
>> copy-editing is happening on these in house. It seems that OUP has
>> adopted new modes of production for these critical editions that
>> create these problems, and authors (and copy-editors?) don't regularly
>> take the time to fix it all. I know in the case of my book the
>> copy-editor, who was otherwise very attentive, didn't seem to have
>> looked at the Greek at all.
>>
>> The other major series of critical texts in Greek (and Latin), on the
>> other hand, the Bibliotheca Teubneriana, has been shuffled from one
>> publisher to another in the last decade. It's now in the hands of De
>> Gruyter, who seems devoted to its revitalization. They're requiring
>> all editors to submit camera-ready-copy, and recommending that they
>> use Critical Edition Typesetter (). I have
>> the impression they only really care about the appearance of the CRC,
>> though, and wouldn't really care if authors prefer other typesetting
>> systems.
>>
>> Jud Herrman
>>
>>
>> On 2010-10-23, John Was
>>  wrote:
>>> OUP will normally be amenable if saving money is in prospect!  I
>>> think the
>>> barrier here has always been the copy-editing process (now more
>>> vulnerable
>>> since house style is not seen as so important and indeed there is no
>>> longer
>>> any copy-editing department at OUP).  A critical edition will normally
>>> require a rather small amount of copy-editing, though there is still the
>>> introduction and commentary to consider - but if a TeX-savvy author is
>>> willing to implement those copy-editing changes and suggestions s/he
>>> agrees
>>> with, there is no real difficulty.  The copy-editor would then
>>> presumably
>>> work by pen(cil) on a draft PDF printout in the traditional way (or by
>>> annotating the PDF electronically, which can be tedious).
>>>
>>> Or of course one can simply trust the author not to make any mistakes at
>>> all, and forgo copy-editing.  Even twenty years ag

Re: [XeTeX] (Xe)LaTeX output in a non-(Xe)LaTeX scholarly community

[Gareth Hughes]

John Was wrote:
> Hello

Hello, John.

> If it's of any interest, I have been using TeX for many years now to
> produce OUP humanities publications (Oxford Studies in Ancient
> Philosophy, recent fascicules of the Medieval Latin Dictionary from
> British Sources [British Academy but published by OUP], and dozens of
> monographs in the field of Greek and Latin, with occasional forays into
> Hebrew and Arabic).  XeTeX has been a great boon but I have always
> stayed clear of LaTeX flavours, for various reasons - initially, if I
> can recall with any accuracy my thoughts of 15 years ago or more,
> because it was at that time rather inflexible (I'm sure I remember a
> handbook which stated that it was so difficult to adjust the
> \baselineskip that those preparing their theses in LaTeX should request
> a dispensation from the normal rule of double spacing).

This is good news, seeing as my experience of OUP has been having to
work with word-processed files. What do you do with fonts? Does OUP give
you their fonts? Otherwise, I would imagine that they would need to make
sure that the font licence allows for commercial publication. At least
with theses, seeing as universities are used to scientist wanting to to
use TeX, they don't get too upset with the rest of us doing so. Even
though double spacing is still ugly, it is not too difficult to achieve.

> However, I only occasionally do naked typesetting, as it were, and am
> normally employed as copy-editor-cum-typesetter, so that I receive
> word-processed files (almost inevitably in Word these days) and work on
> them as I see fit, producing PDFs at the end of the process for the
> manufacturing printer to work with.  I have some very elaborate Word
> macros set up (barely comprehensible to me!) to convert Word italic into
> {\it \/}, footnotes into {\fn{}} etc. (I have double braces
> round my footnotes for reasons that I won't go into), and it all works
> reasonably smoothly - certainly Greek is a breeze now that I don't have
> to convert everything to WordPerfect 5.1 and then into a rebarbative
> transliteration system, as I did when using pure ASCII-based EmTeX.

...and punch holes in cards! I find the problem with many tools for
going from TeX to wp or the reverse is that many try to deal with whole
documents rather than snippets. I would rather write my preamble and
then paste in such converted snippets.

> Interestingly, OUP have recently started requesting my source files
> (viz. .TEX files) for achiving when I hand over the PDFs of a completed
> job, though I'm not sure what use they could ever make of them.  I guess
> their idea is that they might be able to introduce corrections, extra
> bibliography, etc. for future editions in-house, but I rather think that
> with my volumes they will be stumped, particularly after I'm
> institutionalized, buried, or executed for letting through too many typos.

Hah! I can understand why OUP want to archive accessible sources, even
if they can't in reality do anything with them. I wonder if they keep
copies of all those word-processed files too. When I have produced
beamer slides for someone, I included a clearly marked-up source file so
that the presentation could be altered in the future without necessarily
 having to come back to me.

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] (Xe)LaTeX output in a non-(Xe)LaTeX scholarly community

[Gareth Hughes]

McCollum, Adam wrote:
> Dear list members,
> 
> I realize that for publications in math and the sciences using TeX,
> etc. has been common, and perhaps even strongly encouraged or
> required, for many years. It is, alas, not yet at least, so in the
> humanities generally. Thanks to XeLaTeX's ability to work well with
> non-Latin scripts, it is perhaps becoming better known in the fields
> in which I work (Semitic and other eastern languages), but it is
> still somewhat of a surprise, I think, to find colleagues who hear
> "LaTeX" and do not respond with, "What?"! I am writing to ask for
> some thoughts on the predicament of using and enjoying XeLaTeX in my
> work, but not really being able to employ it for anything that will
> be published, since essentially every publisher wants only a .doc or
> .rtf file.

Dear Adam,

Yes, we're in the same predicament: effectively, all potential
publishers want .doc files for submissions. This is useful for the
publisher who wants to let a copy editor play around with the text so
that it meets the house style. Most of the editors in the humanities
wouldn't know what to do with a .tex source file. So, publishers want an
easily editable source file, then they use professional typesetting
software and fonts to produce a PDF for printing. Having worked on
publications through OUP, I think this is the way most of these things
work. If you send a publisher a PDF, they can't edit it (easily and
neatly), they can't easily change your cheap fonts for their expensive
ones, and they can't easily change the layout of the page to book size
with crop marks etc.

There are tools for producing .rtf files from TeX sources, but they're
not nice, particularly because they don't usually understand all the
commands you're using. If you've gone to all the trouble of producing a
good TeX source, why ruin it by trying to squish it into a flaky .rtf?
This could be useful to give the copy editor a visual PDF alongside an
editable .rtf. Either publishers work out how to handle .tex source
files, or they allow authors to do most of the setting themselves (which
latter is what happened with Donald Knuth as far as I recall), or they
let us do it. Somehow I can't see publishers agreeing to send us
hundreds of pounds worth of professional fonts and stand down the
professional typesetters.

It's certainly worth talking with publishers about the problem. Even
though we're traditionally responsible for the text and they for the
context, it has always been a matter of negotiation and compromise. In
the end, the publisher wants something that looks good and fitting and
makes them money. If we can encourage them to work with us using TeX by
showing them the improved results, that's probably the way to move
ahead. Because, I've got all these journal articles in front of me,
published by publishers who specialise in our field, but the errors and
general clumsiness are glaring.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Command \ aemph Already defined

[Gareth Hughes]

@@ wrote:
> Hi,

Hi!

> The syntax of my old files is corrupted apparently because of this error:

Definitions of packages have changed.

> Command \ aemph Already defined.
> Or name \ end ... illegal, see p.192 of The Manual.

Yes, both polyglossia and arabxetex define this command, which creates a
conflict if you load both. I could conceive of the possibility that one
would want both, so perhaps one or other should provide a workaround.

> \documentclass{article}
> \usepackage{bidi}

No need to load bidi, as it will be loaded by other packages.

> \usepackage{xltxtra}

It is probably better to load fontspec instead of xltxtra.
> \usepackage{polyglossia}
> \setmainlanguage{english}
> \setotherlanguage{arabic}

If you remove this command, polyglossia won't define \aemph.

> \usepackage{arabxetex}
> \setmainfont{Lucida Grande} % or your favorite
> \usepackage{geometry}
> 
> \geometry{ hmargin=1.5cm, vmargin=1cm }
> 
> \begin{document}
> 
> \begin{center}
> \begin{arab}[voc]{\Huge}
> {\Huge 'a.hkAmu al-rrA' }
> \end{arab}
> \end{center}
> 
> \begin{center}
> \begin{arab}[trans]
> %{al-?ay? al-`?lim Na??r al-D?n al-??s?}
>  \Large
> \textit{'a.hkAmu al-rrA'}\textrm{ ( Règles du Ra)}
> \end{arab}
> \end{center}
> \end{document}
> 
> 
> Where can I find this command in order to correct it? How should reorder my
> packages?
> 
> 
> Regards
> --
> @@
> --

GG.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] polyglossia/bidi -- footnote rule alignment

[Gareth Hughes]

Khaled Hosny wrote:
> On Thu, Oct 14, 2010 at 12:58:15PM -0400, Kamal Abdali wrote:
>> Dear Gareth,
>>
>> Thanks for pointing out the better polyglossia style (\setmainfont).
> 
> I think defining an \urdufont is better than setting it globally using
> \setmainfont (neither is a polyglossia command) in case your Urdu font
> has no Latin characters or you want to use a different Latin font, as
> the former will be used inside Urdu environments only.

Khaled, I would want to debate this. The two fontspec methods, setting
\urdufont and setting \mainfont, are equivalent for Urdu-language
document. It seems that most non-Latin fonts have glyphs filling the
ASCII repertoire as a matter of course. However, these just-in-case
glyphs are probably not fit for quality typesetting. I believe the
polyglossia way is right here: use \setromanfont to declare a quality
Roman font, this defines it as \normalfontlatin while allowing the Urdu
font to be \normalfont. I think this is a more logical approach to a
non-Latin document, that Latin fonts, if required, are defined as
subsidiary, rather than the other way round. Of course, either way will
work, but this seems to make more sense.

Kamal Abdali wrote:
> As to the main problem, Vafa Khalighi has kindly explained that for the
> footnoterule to be aligned correctly, the RTLdocument or rldocument option
> of bidi has to be activated. Apparently, this has not been done by
> polyglossia.
> 
> He has also recommended \autofootnoterule instead \rightfootnoterule.
> 
> That takes care of the problem. It is too easily fixed to require any change
> in polyglossia or its language-specific files.

I had expected that polyglossia automatically selected RTLdocument from
bidi's options when \setdefaultlanguage is an RTL language. This is
important information for me, because the Syriac package I'm writing
makes this assumption too.

I can see how \autofootnoterule is preferable just in case you set some
LTR footnotes too.

For me, the joy of polyglossia is that it interfaces with bidi so that I
don't have to type bidi commands all over the place (the pre-polyglossia
documents I have are littered with these commands every time I want to
change to a language in a different direction). Polyglossia helps make
multilingual typesetting a bit more streamlined. So, I wonder whether
François might want to comment about this. What other issues might arise
when an RTL document is set with bidi when RTLdocument is not selected?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] polyglossia/bidi -- footnote rule alignment

[Gareth Hughes]

Kamal Abdali wrote:
> I'm using the package polyglossia to typeset documents in Urdu, a
> right-to-left language. Polyglossia uses the bidi package whose
> documentation implies that the footnote rule is right-aligned when the
> footnote is in the middle of some right-to-left text. But the footnote rule
> is appearing aligned to the left anyway.
> 
> Here is an example:
> 
> \documentclass{article}
> \usepackage{polyglossia}
> \setmainlanguage{urdu}
> \newfontfamily\urdufont[Script=Arabic,Scale=1.7]{Lateef}
> %\rightfootnoterule   %force footnote rule to right
> \begin{document}
> افلاطون
> \footnote{یونانی فلسفی}
> \end{document}
> 
> 
> Unless the commented statement is uncommented, the footnote rule shows up on
> the left.
> 
> Kamal Abdali

Dear Kamal,

I can confirm that the footnote rule is wrongly positioned in your file.
I thought that changing \newfontfamily\urdufont for \setmainfont might
make a difference, but it doesn't (I think this replacement might be
considered more correct in polyglossia). As you say, the footnote rule
needs to be forced to be placed correctly.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem for dialogue poetry

[Gareth Hughes]

Paul Isambert wrote:
> Ok, the following works on your file, but I don't know how robust it is:
> 
> %%%
> 
> \newcount\LineNumber \newcount\templinenumber
> \newdimen\linenumberskip \linenumberskip=6em
> \chardef\linestep=2
> \def\poemlinenumber{%
>   \advance\LineNumber1
>   \templinenumber=\LineNumber
>   \computelinenumber
>   }
> \def\computelinenumber{%
>   \ifnum\templinenumber>\linestep
> \advance\templinenumber-\linestep
> \expandafter\computelinenumber
>   \else
> \ifnum\templinenumber=\linestep
>   \leavevmode\rlap{\kern\linenumberskip\the\LineNumber}%
> \fi
>   \fi
>   }
> \newenvironment{numberedpoem}
>   {\everypar{\everypar{\poemlinenumber}}%
>\begin{traditionalpoem}}
>   {\end{traditionalpoem}}
> 
> %%%
> 
> You poem should now be enclosed in the "numberedpoem" environment.
> You can change \linestep (on line 3) to any value; if it is set /n/,
> every /n/th line number is printed.
> You can change \linenumberskip (on line 2), which sets the distance of
> the line number to the margin.
> This is not thoroughly tested! Sorry for the syntax, it's not LaTeX-like
> (but you made me -- although you didn't ask! -- download so many
> packages so your file can work than I need a little revenge :) ).
> 
> Best,
> Paul


Thank you, Paul, for showing me how to do this. It looks good and is
quite flexible. I have a couple more questions, if I may.

1) What is the best way of changing the positioning of the numbers so
that they are on the right of the poem, or that they are on the inner or
outer edge in documents that define these things? Is this best done by
altering \linenumberskip?

2) As it stands, a blank line, indicating a stanza break, is counted as
a line of the poem. How can this code be altered so as not to count the
blank lines between stanzas?

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] New environment fails in float

[Gareth Hughes]

I'm having problems with an environment definition. Using the xparse and
etoolbox packages, I have created the environment syriacpoem in my .sty
file. It is defined as

%%
\DeclareDocumentEnvironment{syriacpoem}{so}{%
  \ifbool{...@kashpoem}{\begin{syrjust}}{}%
\begin{syriac}%
  \ifstrequal{#2}{estr}{\estrfont}{}%
  \ifstrequal{#2}{serto}{\sertofont}{}%
  \ifstrequal{#2}{madnha}{\madnhafont}{}%
  \ifstrequal{#2}{east}{\madnhafont}{}%
  \ifstrequal{#2}{estrangelo}{\estrfont}{}%
  \ifstrequal{#2}{estrangela}{\estrfont}{}%
  \IfBooleanTF #1 {\begin{traditionalpoem*}}{\begin{traditionalpoem}}}{%
  \IfBooleanTF #1
{\end{traditionalpoem*}}{\end{traditionalpoem}}\end{syriac}%
  \ifbool{...@kashpoem}{\end{syrjust}}{}}
%%

The boolean x...@kashpoem is true if word-stretching justification is
required. The environment syrjust provides that justification using a
version of Jonathan Kew and Fr Michael Gilmary's implementation with
interchartoks shown on this list. The syriac environment is from
polyglossia, ensuring RTL and a Syriac font, and it is followed by
optional font switches for other Syriac fonts. Then either the starred
or unstarred version of bidipoem's traditionalpoem environment is turned
on depending on the presence or absence of a star in the document
command. The end of environment closes all these nested environments in
order.

This new environment works as expected in normal tests. However, as I
came to document it, I wanted to give an example in a framed float in my
package documentation. However, the new environment breaks inside the
float. My framed box uses the fancybox package and is defined as

%%
\newenvironment{example}[1]%
  {\begin{figure}[h]\begin{center}\begin{Sbox}\begin{minipage}{#1}}%
  {\end{minipage}\end{Sbox}\ovalbox{\TheSbox}\end{center}\end{figure}}
%%

Obviously, something in the environment is upsetting my example box. If
I replace my syriacpoem environment with the nested environments it
calls, it works perfectly. So, there's nothing wrong with what the
environment does, just in how it does it. The lengthy section of the log
dealing with this is below. Can anyone suggest how to fix this?

Thanks,

Gareth.

Log extract follows:

! Missing number, treated as zero.

   \group_end:
l.314 ^^I\end{syriacpoem}

A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)


! LaTeX Error: \begin{traditionalpoem*} on input line 305 ended by
\end{traditi
onalpoem}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.314 ^^I\end{syriacpoem}

Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

! Extra }, or forgotten \endgroup.
\endminipage ...pagefalse \co...@endgroup \egroup
  \...@rtl \endL \fi
\egroup ...
l.316 ^^I\end{example}

I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.

! Extra }, or forgotten \endgroup.
\endminipage ...\egroup \...@rtl \endL \fi \egroup
  \egroup \expandafter
\...@iii...
l.316 ^^I\end{example}

I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.

! Extra }, or forgotten \endgroup.
\endminipage ..@rtl \endL \fi \egroup \egroup
  \expandafter
\...@iiiparbox \...
l.316 ^^I\end{example}

I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.


! LaTeX Error: Misplaced \endSbox! Should be in LR mode.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.316 ^^I\end{example}

You're in trouble here.  Try typingto proceed.
If that doesn't work, type  X   to quit.


! LaTeX Error: \begin{minipage} on input line 304 ended by \end{Sbox}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.316 ^^I\end{example}

Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

! Missing } inserted.

}
l.316 ^^I\end{example}

I've inserted something that you may have forgotten.
(See the  above.)
With luck, this will get me unwedged. But if you
really didn't forget anything,

Re: [XeTeX] Font nuisances

[Gareth Hughes]

Fr. Michael Gilmary wrote:
> Oh, now I see what you're trying to do ... and what you've got here,
> Gareth, works for me. You can also use:
> 
> \setmainfont[ItalicFont={BergamoStd-Italic},
> BoldFont={BergamoStd-Bold},
> BoldItalicFont={BergamoStd-BoldItalic}]{Cardo}

Yes, it looks like fontspec allows either the full name {Bergamo Std
Bold Italic} or the PostScript name {BergamoStd-BoldItalic}. Oddly, it
will allow the compromise of {Bergamo Std-Bold Italic}, with the full
name with a PostScript-style hyphen between the family name and the
subfamily name, and that's it. Trying to give the full family name with
the PS subfamily name will not work.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Font nuisances

[Gareth Hughes]

Dear David,

The errors you have been getting are font-not-found errors. I've never
been entirely sure which names fontspec likes for these derived faces.
However, the following works for me:

\setmainfont[ItalicFont={Bergamo Std Italic}, BoldFont={Bergamo Std
Bold}, BoldItalicFont={Bergamo Std Bold Italic}]{Cardo}

I would usually put hyphens in these names, and the following also works.

\setmainfont[ItalicFont={Bergamo Std-Italic}, BoldFont={Bergamo
Std-Bold}, BoldItalicFont={Bergamo Std-Bold Italic}]{Cardo}

However, what doesn't work is Bergamo Std-BoldItalic. Hence the errors.

Gareth.

David Perry wrote:
> Yes, I just realized that my example from the fontspec manual was not
> exactly parallel to the situation I have.  However, doing it as Gareth
> suggests generates all sorts of nasty error messages.
> 
> I just tried specifying the bold etc. by font file names; no errors, but
> no bold in the document either.
> 
> I'll study this more tomorrow when my brain is working better.
> 
> David
> 
> On 10/10/2010 11:19 PM, Andy Lin wrote:
>> Gareth is right; that is how you use BoldFont. Take a look at the
>> example from the fontspec manual again. It's using the HN-Regular as
>> the bold font because it's heavier than HN-Ultralight.
>>
>> -Andy
>>
>> On Sun, Oct 10, 2010 at 23:05, David Perry 
>> wrote:
>>>

>
> 2. Can anybody see what is wrong with the following?
>
> \fontspec[BoldFont={Bergamo Std},ItalicFont={Bergamo
> Std},BoldItalicFont={Bergamo Std}]{Cardo}

 Yeah, you just declared the medium, upright font as bold and italic.
 What you need is

 \fontspec[BoldFont={Bergamo Std-Bold}, ItalicFont={Bergamo Std-Italic},
 BoldItalicFont={Bergamo St-BoldItalic}]{Cardo}

>>> I don't think so.  See example 4 in the most recent fontspec manual,
>>> from
>>> which I copied this:
>>>
>>> \fontspec[BoldFont={Helvetica Neue}]{Helvetica Neue UltraLight}
>>>
>>> which makes Helvetica Neue act as the "bold" for Helvetica Neue
>>> Ultralight.
>>
>>
>>
>> --
>> Subscriptions, Archive, and List information, etc.:
>>http://tug.org/mailman/listinfo/xetex
>>
>>
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Font nuisances

[Gareth Hughes]

David Perry wrote:
> This seems to be my day for font problems.
> 
> 1. What is the correct way to specify a font in exact point size when
> running XeLaTeX?  (This is for the cover page of a book where \Huge
> isn't big enough.)  The LaTeX command \fontsize{60}{66pt} does not work
> -- it comes out much smaller than 60 pts, although there is no
> compilation error.

I'm not sure that thinking about the point size in absolute terms is all
that useful. If the body text is at 12pt, then something that is at 60pt
is five times bigger. I would use \addfontfeature{Scale=5} for a single
line of text, like a title. Otherwise, the package anyfontsize will
allow \fontsize{60pt}{66pt} to work.

> 
> 2. Can anybody see what is wrong with the following?
> 
> \fontspec[BoldFont={Bergamo Std},ItalicFont={Bergamo
> Std},BoldItalicFont={Bergamo Std}]{Cardo}

Yeah, you just declared the medium, upright font as bold and italic.
What you need is

\fontspec[BoldFont={Bergamo Std-Bold}, ItalicFont={Bergamo Std-Italic},
BoldItalicFont={Bergamo St-BoldItalic}]{Cardo}

> Cardo has no bold, italic, or bold italic versions, so I'm using Bergamo
> for the moment.
> 
> I can confirm:
> a) all the fonts are installed in Windows font folder and can be used in
> a Word document
> 
> b) the log file looks as though the family is being defined correctly
> (see extract below) yet nothing happens in the document when I issue
> \textbf{blah} and so forth.
> 
> c) Cardo has TrueType outlines while Bergamo has CFF outlines; could
> this cause a problem?  (I wouldn't think so, but you never know.)

No, this makes no difference.

> Thanks - David

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem for dialogue poetry

[Gareth Hughes]

Paul Isambert wrote:
> That one is harder. Line number are no simple matter with traditional TeX.
> Question: does bidipoem starts a new paragraph with every line? Then
> something might be doable with \everypar.
> Just try this in the poem environment: \everypar{test}. If ``test''
> appears at the beginning of every line, then I might try to find a
> solution.

Hmm. Within the environment \everypar has no effect, but given outside
the traditional poem, but within the font changing environment, it
prints on each line including the  the 'zeroth' line. I'm not sure if
this is the right way to do this, how might this work?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem for dialogue poetry

[Gareth Hughes]

Paul Isambert wrote:
>  Le 10/10/2010 14:16, Philip Taylor (Webmaster, Ret'd) a écrit :
>> Paul, in which dialect(s) of TeX does \quitvmode exist ?
>>
>> Paul Isambert wrote:
>>
>>> \def\persona#1{%
>>> \quitvmode\llap{\hbox to {#1\hfil}}%
>>> }
>>
> 
> Oh, right.
> Gareth, you should use \leavevmode instead of \quitvmode, which is a
> pdfTeX primitive that doesn't exist in XeTeX.
> 
> Paul

Yes, I spotted that \leavevmode was intended. Thank you, Paul, that
works like a dream and means that I don't have to use \phantom boxes
repeatedly.

Does anyone have any thoughts how line numbers might be handled in this
bidipoem environment? None of the usual packages that provide line
numbering play nicely, and I can't work out from the code how best to do it.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem for dialogue poetry

[Gareth Hughes]

Gareth Hughes wrote:
> As you can see from my attached example, the persona is included as a
> part of the first hemistich, but to make the lines look nice it is also
> included in the following three hemistiches within \phantom{} commands.
> I also need to set \poemcolsep to -1em to close the 'phantom' gap. I
> hope that makes sense.
> 
> Well, the problem is that it's not a pretty workaround and the beginning
> of the first hemistich of each line doesn't line up, because personae
> are of different lengths. I suppose I need some means of marking up each
> line as having
> 
>   persona: first-hemistich & second-hemistich

OK. I think \llap is useful here to give the personae and there phantom
versions zero width aligned right.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Bidipoem for dialogue poetry

[Gareth Hughes]

Shlama Mezdathkane (Hi XeTeXnicians)!

I'm using bidipoem to set some Syriac dialogue poems. I'm using the
traditionalpoem environment as each line is fourteen syllable long with
a caesura after the seventh syllable. So far, so good. However, as it's
a dialogue poem the speaker changes every other line, and these lines
are introduced with the name of the speaker followed by a colon.

As you can see from my attached example, the persona is included as a
part of the first hemistich, but to make the lines look nice it is also
included in the following three hemistiches within \phantom{} commands.
I also need to set \poemcolsep to -1em to close the 'phantom' gap. I
hope that makes sense.

Well, the problem is that it's not a pretty workaround and the beginning
of the first hemistich of each line doesn't line up, because personae
are of different lengths. I suppose I need some means of marking up each
line as having

persona: first-hemistich & second-hemistich

and then working out how to set them properly. Any ideas how best to go
about this?

Thanks,

Gareth.


bidipoem-test.pdf
Description: Adobe PDF document
\documentclass[12pt]{minimal}
\usepackage{polyglossia, bidipoem}
% Begin justification stuff
\chardef\zwj="200D
\chardef\ksh="0640
\chardef\D=10
\chardef\L=11
\chardef\R=12
\chardef\A=13
\chardef\V=256
\def\stretch{\zwj\nobreak \setbox0=\hbox{\ksh}%
\leaders\hrule height\ht0 \hskip0pt plus 0.5em \zwj}
\def\setclass#1#2{\def\theclass{#1}\def\charlist{#2}%
  \expandafter\dosetclass\charlist,\end}
\def\dosetclass#1,#2\end{%
  \def\test{#1}\def\charlist{#2}%
  \ifx\test\empty\let\next\finishsetclass
  \else\XeTeXcharclass"\test=\theclass
 \let\next\dosetclass\fi
  \expandafter\next\charlist,,\end}
\def\finishsetclass#1,,\end{}
\setclass\A{0710}
\setclass\R{0715,0717,0718,0721,0728,072A,072C}
\setclass\D{0712,0713,071A,071B,071D,071F}
\setclass\D{0722,0723,0725,0729,072B}
\setclass\L{0720}
\setclass\V{0730,0731,0732,0733,0734,0735}
\setclass\V{0736,0737,0738,0739,073A,073B,073C}
\setclass\V{073D,073E,073F,0740,0741,0742,0743}
\setclass\V{0744,0745,0746,0747,0748}
\setclass\V{00AB,00BB}
\XeTeXinterchartoks\D\D={\stretch}%
	\XeTeXinterchartoks\L\D={\stretch}%
	\XeTeXinterchartoks\D\L={\stretch}%
	\XeTeXinterchartoks\L\L={\stretch}%
	\XeTeXinterchartoks\D\R={\stretch}%
	\XeTeXinterchartoks\D\A={\stretch}%
	\XeTeXinterchartoks\L\R={\stretch}%
	\XeTeXinterchartoks\L\A={}%
	\XeTeXinterchartokenstate=1
\setclass \A {0710}
\setclass \R {0715,0717,0718,0721,0728,072A,072C}
\setclass \D {0712,0713,071A,071B,071D,071F}
\setclass \D {0722,0723,0725,0729,072B}
\setclass \L {0720}
\setclass \V {0730,0731,0732,0733,0734,0735}
\setclass \V {0736,0737,0738,0739,073A,073B,073C}
\setclass \V {073D,073E,073F,0740,0741,0742,0743}
\setclass \V {0744,0745,0746,0747,0748}
% End justification stuff

\setmainlanguage{syriac}
\setmainfont[Script=Syriac]{Serto Jerusalem}
\renewcommand\poemcolsepskip{-1em}
\begin{document}
\begin{traditionalpoem}
		ܟܪܘܒ: %
		 ܠܴܐ ܡܶܫܟܰܚ ܐܱܢ̱ܬ ܕܬܷܥܘܿܠ ܠܟܳܐ&%
		\phantom{ܟܪܘܒ: }%
		ܕܰܐܬܪܱܐ ܗ̇ܘ ܙܰܗܝܳܐ ܘܠܴܐ ܡܶܬܕܪܫ.\\
		\phantom{ܟܪܘܒ: }%
		ܫܟܺܝܢܬܴܐ ܒܓܰܘܗ ܡܶܙܕܰܝܚܳܐ&%
		\phantom{ܟܪܘܒ: }%
		ܘܪܘܼܡܚܳܐ ܕܢ݀ܘܪܴܐ ܠܷܗ ܢܴ̇ܛܪܴܐ܀\\
		ܓܝ̇ܣܐ: %
		ܠܴܐ ܡܶܫܟܰܚ ܐܱܢ̱ܬ ܕܬܷܟܠܹܐ ܠܐ ܢܳܫ&%
		\phantom{ܓܝ̇ܣܐ: }%
		ܩܗܳܬ݀ ܠܴܗ̇ ܪܘܡܚܳܐ ܘܶܐܫܬܱܗܝܲܬ݀.\\
		\phantom{ܓܝ̇ܣܐ: }%
		ܙܩܝܼܦܴܐ ܦܱܬܚܗ̇ ܠܓܲܢܬ ܥܕܶܝܢ&%
		\phantom{ܓܝ̇ܣܐ: }%
		ܘܠܴܐ ܐܻܝܬ ܦܘܪܣܳܐ ܕܬܾܘܒ ܬܷܬܚܕ܀
\end{traditionalpoem}
\end{document}


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] parallel lines for multiple text versions

[Gareth Hughes]

James Crippen wrote:>
> A newer and more flexible system is John Frampton’s expex.
> 
> http://www.math.neu.edu/ling/tex/
> 
> It works quite well and is very well documented. It uses only TeX, but
> works fine in a LaTeX environment.

This looks nice. Is there a reason why it's not on CTAN?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] parallel lines for multiple text versions

[Gareth Hughes]

Andy Lin wrote:
> You can take a look at the gb4e package (or its predecessor
> covington). It was designed for glosses in linguistics, but the
> mechanism might suit your needs. It takes up to 3 lines of input,
> reads the first word (or group) of each line, puts those in a box,
> then reads the next word and puts those in a box... and so on. In this
> way, long lines will break at the same word/group for all 3 lines.
> 
> The way you could adapt it for your use is to enter the lines
> normally, but group each of them with curly brackets. That will
> prevent the package from separating it into individual words. For long
> lines, make two groups, starting the second group where you want the
> line break to occur.
> 
> -Andy
> 
> On Tue, Oct 5, 2010 at 22:18, Adam McCollum  wrote:
>> Dear list members,
>>
>> I have a formatting question. What I would like to do is give line by line
>> three versions of a certain text (in this case, different recensions of the
>> Gospel of Matthew in Ge'ez, i.e. classical Ethiopic). In a WYSIWYG program,
>> I can of course just eyeball where the line breaks need to be and make them
>> manually. The process is somewhat more complicated by the fact that I'd like
>> to have each verse somewhat separated from other verses, and this means that
>> when the verse extends more than one line, the breaks still have to coincide
>> for each version. I'm not sure if I've done a good job explaining what I'm
>> hoping to do, so I attach a PDF sample written in a WYSIWYG program.
>>
>> Many thanks in advance for any help!

I've used covington before with good results. The 'glosses' environment
is useful for setting interlinear glosses, translations etc. I hadn't
heard of the gb4e package Andy mentioned before, but it looks good, and
seems to do the same thing with glosses. Covington can cope with RTL
text too.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] arabxetex vs. xepersian

[Gareth Hughes]

Ross Moore wrote:
> There is a big compatibility problem with this package, which really
> should be fixed before it gets distributed widely.
> 
> The choices of some of the macro-names are rather unfortunate,
> since they clash with existing, long-standing uses for those names.
> 
> \A = Å
> \L = Ł
> \R  is undefined, but is often used privately for  ℝ
> \D  is undefined, but is often used privately for  ⅅ
> \V  is undefined
> 
> Using single-letter macro names is always dangerous,
> due to clashes of this kind.
> It is especially damaging when your document has bibliographic
> entries, with authors names requiring the letters whose macros
> have now been redefined.
> 
> I would suggest changing all the definitions and uses within
> the package to names such as:
> 
>   \kshdA  \kshdD   \kshdL  \kshdR  \kshdV

I had thought of this, and renamed these with the xsy@ prefix seeing as
they should only operate internally within the package.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] arabxetex vs. xepersian

[Gareth Hughes]

Axel Kielhorn wrote:
> Am 03.10.2010 um 22:41 schrieb Gareth Hughes:
> 
>> ArabXeTeX does a similar job to Polyglossia when it comes to font
>> set-up and commands for language change. However, ArabXeTeX
>> specialises in using input in Latin transliteration to render
>> Arabic. It is designed to work with the various languages that use
>> Arabic-derived scripts. I don't find this that useful (though I
>> know some do, and respect their preference), seeing as I can enter
>> both Arabic and the Latin diacritics needed for scientific
>> transliteration in Unicode.
> 
> If I understand it correctly, latin input is just an option. It will
> be processed by TECkit into Unicode.

Yes, it has a very nice implementation of TECkit. Of course it's an
option, but it's a major feature available in ArabXeTeX.

>> XePersian does something completely different. It adds some
>> valuable tools that refine Persian typesetting. It adds /kashida/
>> justification and Persian-language aliases for commands (it's
>> annoying to have to change script/keyboard and text direction to
>> enter commands).
> 
> I now see that kashida is xepersian only, I need to mention that.
> 
> I remember a discussion about using kashida in other languages as
> well but haven't seen anything in the documentation.

Fr Michael Gilmary adapted Jonathan Kew's code for Syriac, and I'm
including that in my forthcoming Syriac package.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] arabxetex vs. xepersian

[Gareth Hughes]

Axel Kielhorn wrote:
> Reading the documentation of the XeTeX packages I want to mention in lshort, 
> I came across two packages for Farsi:
> 
> arabxtex supports:
> arab (Arabic)
> farsi (persian)
> urdu
> sindhi
> pashto
> ottoman (turk)
> kurdish
> kashmiri
> malay (jawi)
> uighur
> 
> xepersian supports only Farsi, but adds command names in Farsi as well.
> 
> The later seems to be aimed at native speakers.
> Is there any reason to prefer one over the other?
> 
> At the same time I noticed that there is no package for Hebrew.
> Is bidi (and a correct font) sufficient to write Hebrew?
> 
> Are there any fonts recommended for either language?
> 
> Axel

Hi Axel!

It seems there has been more heat than light on this issue. RTL
typesetting is possible natively under XeTeX. Bidi seriously refines and
simplifies this, so that now I would never attempt RTL typesetting
without it. Polyglossia is the Babel replacement, and it interfaces
nicely with Bidi when RTL languages are selected.

ArabXeTeX does a similar job to Polyglossia when it comes to font set-up
and commands for language change. However, ArabXeTeX specialises in
using input in Latin transliteration to render Arabic. It is designed to
work with the various languages that use Arabic-derived scripts. I don't
find this that useful (though I know some do, and respect their
preference), seeing as I can enter both Arabic and the Latin diacritics
needed for scientific transliteration in Unicode.

XePersian does something completely different. It adds some valuable
tools that refine Persian typesetting. It adds /kashida/ justification
and Persian-language aliases for commands (it's annoying to have to
change script/keyboard and text direction to enter commands). XePersian
also defines commands for setting up fonts, like Polyglossia and
ArabXeTeX. It also provides commands for setting up a range of Persian
fonts in traditional (and not so traditional) shapes, in a similar
fashion to the TeX trinity of roman, sans and mono.

Apologies to the venerable authors of these packages if I have
misunderstood their artistry.

I hope this helps.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] polyglossia overline on a number of lines (another attempt)

[Gareth Hughes]

Vafa Khalighi wrote:
> Use umonline package:
> http://tug.ctan.org/cgi-bin/ctanPackageInformation.py?id=umoline

وفا!
I can't get umoline to play nicely in Syriac. Can you actually typeset
multiline Persian with \Overline?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Redefining \em and \emph

[Gareth Hughes]

Will Robertson wrote:
> On 2010-09-25 09:33:20 +0930, Gareth Hughes  said:
> 
>> Will Robertson wrote:
>>> It doesn't seem to. In that case I'd write something like
>>>
>>> \let\oldemph\emph
>>> \renewcommand\emph{%
>>> \...@rtl \expandafter\aemph \else \expandafter\oldelse \fi
>>> }
>>
>> I still can't figure out how to do this for \eminnershape as defined in
>> fixltx2e. Any suggestions how to do that?
> 
> Do you mean so that you can write
> 
>\aemph{ ... \aemph{ ...} ... }
> 
> and have the inner \aemph not put the overline on top? In this case, you
> can write (and this might be a reasonable addition to polyglossia)
> 
> \documentclass{article}
> \makeatletter
> \def\aemph#1{%
>  \begingroup
>\let\aemph\inneraemph
>$\overline{\hbox{#1}}$%
>  \endgroup
> }
> \def\inneraemph#1{%
>  \egroup% close \hbox
>  \egroup% close \overline
>  $% close math
>  {\eminnershape #1}% inner emphasis!
>  $% "reopen" math
>  \expandafter\overline\bgroup % "reopen" \overline
>  \hbox\bgroup % "reopen" \hbox
> }
> \makeatother
> \begin{document}
> hello there \aemph{foo \aemph{oof rab} bar} baz black
> \end{document}
> 
> Modulo checks for bidi and using \hboxR instead of \hbox and a "correct"
> definition for \eminnershape in this context, and so on. But this has
> nothing to do with the idea of \eminnershape: if you want to tie the two
> together, fontspec actually overrides fixltx2e's emph/eminnershape code:
> 
> \ExplSynaxOn
> \DeclareRobustCommand \em {
>  \...@nomath\em
>  \tl_if_eq:xxTF \...@shape \itdefault \eminnershape
>  {
>\tl_if_eq:xxTF \...@shape \sldefault \eminnershape \emshape
>  }
> }
> \DeclareTextFontCommand{\emph}{\em}
> \cs_set_eq:NN \emshape \itshape
> \cs_set_eq:NN \eminnershape \upshape
> \ExplSyntaxOff
> 
> Not sure if that helps directly...
> 
> Will

That is really interesting. My understanding of plain TeX is getting
better, but still rudimentary. The Expl3 stuff is beyond me at the moment.

I'm trying to write a package for writing Syriac under XeLaTeX, and part
of it is to allow the end user some simple commands to redefine emphasis
and inner emphasis for Syriac text. These might be changing text colour
(common in manuscripts), putting dots around text, overlining (\aemph),
changing the font style (using a Syriac style called Estrangelo) etc. I
think I'm trying to do too much, but I think it's possible. My muddled
and messy code is shown below. Any help greatly appreciated.

Thanks,

Gareth.

%
% \subsection{Emphasis styles}
%\begin{macro}{\emphcolour}
%\begin{macro}{\emphstyle}
% Define commands for changing emphasis.
%\begin{macrocode}
\newcommand\emphcolour{\crimson}
\newcommand\...@emphestr{\ifdef{\estrfont}{\renewcommand\emshape{\estrfont}}%
{\renewcommand\emshape{\syriacfont}}}
\newcommand\...@emphaemph{%
\let\oldemph\emph
\renewcommand\emph{%
\...@rtl \expandafter\aemph \else \expandafter\oldemph \fi}}
\newcommand\...@emphred{\let\oldemph\emph
\renewcommand\emph{...@rtl \expandafter\emphcolour %
\else \expandafter\oldemph \fi}}
\newlength{\...@dashwidth}\setlength{\dashdash}{.075em}\setlength{\fboxsep}{.15em}
\newcommand\...@dashbox[1]{\settowidth{\xsy@dashwidth}{#1}%
\addtolength{\...@dashwidth}{.15em}\dashbox[\xsy@dashwidth][c]{#1}}
\newcommand\...@emphdash{\let\oldemph\emph
\renewcommand\emph{...@rtl \expandafter\...@dashbox %
\else \expandafter\oldemph \fi}}
\newcommand\emphstyle[1]{%
\ifstrequal{#1}{italic}{\renewcommand\emshape{\itshape}}{}%
\ifstrequal{#1}{overline}{\...@emphaemph}{}%
\ifstrequal{#1}{red}{\...@emphred}{}%
\ifstrequal{#1}{estr}{\...@emphestr}{}%
\ifstrequal{#1}{estrangelo}{\...@emphestr}{}%
\ifstrequal{#1}{estrangela}{\...@emphestr}{}%
\ifstrequal{#1}{slanted}{%

\renewcommand\emshape{\addfontfeature{AutoFakeSlant=-0.3}\slshape}}{}%
\ifstrequal{#1}{outline}{\renewcommand\emshape{\outlshape}}{}%
\ifstrequal{#1}{dotted}{\...@emphdash}{}}
%\end{macrocode}
%\end{macro}\end{macro}
%\begin{macro}{\inneremphcolour}
%\begin{macro}{\inneremphstyle}
% Define commands for changing inner emphasis.
%\begin{macrocode}
\newcommand\inneremphcolour{\gold}
\newcommand\...@inneremphestr{\ifdef{\estrfont}%
{\renewcommand\eminnershape{\estrfont}}%
{\renewcommand\eminnershape{\syriacfont}}}
\newcommand\...@inneremphaemph{%
\let\oldeminnershape\eminnershape
\renewcommand\eminnershape{%
\...@rtl \expandafter\aemph \else \oldeminnershape \fi}

Re: [XeTeX] Redefining \em and \emph

[Gareth Hughes]

Will Robertson wrote:
> It doesn't seem to. In that case I'd write something like
> 
> \let\oldemph\emph
> \renewcommand\emph{%
>  \...@rtl \expandafter\aemph \else \expandafter\oldelse \fi
> }

I still can't figure out how to do this for \eminnershape as defined in
fixltx2e. Any suggestions how to do that?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Redefining \em and \emph

[Gareth Hughes]

Vafa Khalighi wrote:
> I have not been following this so far but this should not be included in
> either polyglossia or fontspec at least for Persian because we use slanted,
> italic or what we call Khabideh in Persian.


Don't panic! I'm simply planning to provide a package option for a
Syriac package I'm writing to allow users to turn \emph into an alias
for \aemph within RTL environments. Slanted text is not traditional in
Syriac, but has been used more recently. It looks quite ugly. I imagine
that proper khabideh in fonts involves special shapes that are more than
the addition of slant.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Redefining \em and \emph

[Gareth Hughes]

Philip Taylor (Webmaster, Ret'd) wrote:
> 
> 
> Will Robertson wrote:
> 
>> I'd write something like
>>
>> \let\oldemph\emph
>> \renewcommand\emph{%
>> \...@rtl \expandafter\aemph \else \expandafter\oldelse \fi
> 
> or better still, ... \expandafter \oldemph \fi %!
> ** Phil.

Yes, I'd spotted that. Thanks Will for this. For someone who doesn't
know much TeX, this is really enlightening. Is there a way of adapting
this to modify inner emphasis?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Redefining \em and \emph

[Gareth Hughes]

Will Robertson wrote:
> On 2010-09-23 09:07:39 +0930, Gareth Hughes  said:
> 
>> I'm looking at ways to redefine emphasis within Syriac text (seeing as
>> slanted text is not traditional or pretty). I've got most of the
>> redefinitions working, but I'd also like to redefine \emph as an alias
>> for \aemph in Syriac text. What's the best way of doing that?
> 
> Good question.
> I'm not very familiar with multilingual typesetting -- how do you switch
> fonts? Is there a switch that you can query in this case?

I think the most obvious query would be directionality, so \...@rtl from
Vafa's bidi package might be the appropriate test: it would be true for
Syriac (and Persian etc.) and false for English (and Korean etc.). I
don't know if polyglossia has any language conditionals, but that would
give finer control. This is probably of more use than a font switch
(\syriacfont), for which I might have to create an exception if Syriac
were \normalfont.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Redefining \em and \emph

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

As I understand it, the line about redefining emphasis and inner
emphasis at the end of section 6.3 of the fontspec documentation

> XETEX users will need to load the xltxtra package before the advice above 
> works.

is no longer true seeing as fontspec-patches now does this, and fontspec
loads it automatically.

I'm looking at ways to redefine emphasis within Syriac text (seeing as
slanted text is not traditional or pretty). I've got most of the
redefinitions working, but I'd also like to redefine \emph as an alias
for \aemph in Syriac text. What's the best way of doing that?

Thanks,

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMmpND9UDttp8yrx4RAt4sAJ45TrVRulQol6vU24Tm6RXXdHW1gwCfdycg
9dPxU4mVfBn1JJpavEoaFOg=
=wShw
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] If font under fontspec

[Gareth Hughes]

Michiel Kamermans wrote:
> Purely from a production point of view: if you have a document for which
> it is important the right fonts are available, making sure the fonts are
> available to whomever needs to compile it might deserve consideration
> too. So that rather than trying to "fix" the source, you throw a compile
> error that the user does not have the prerequisite fonts to accurately
> generate the document that was intended to be generated.
> 
> Just thinking along the original TeX idea that "If it compiles, the
> result is the same for every system it successfully compiles on".

Yes, I can understand your reasoning here. Though perhaps I should have
explained myself better in the first place. The Syriac font Estrangelo
Edessa leaves noticeable white space before the letter ܓ when it is
preceded by a non-joining letter. It seems this is a carry over from old
metal type. Some people see it as a feature rather than a bug, but I
wanted to provide a fairly smart user command for closing up that white
space, and have written something with \XeTeXinterchartoks to do so.
However, it is important that this kerning isn't applied when other
Syriac fonts, which have no gap, are being set.

I hope that makes the situation a little more clear.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] If font under fontspec

[Gareth Hughes]

Will Robertson wrote:
> It sort of depends how you want to write the code for the test. Here's a
> proof of concept that might do what you need:
> 
> \documentclass{article}
> \usepackage{fontspec}
> 
> \makeatletter
> \newcommand\IsFont[4][]{%
>  \begingroup
>\let\curr...@family\f@family
>\fontspec[#1]{#2}
>\ifx\curr...@family\zf@family
>  \global\l...@tempa\@firstoftwo
>\else
>  \global\l...@tempa\@secondoftwo
>\fi
>  \endgroup
>  \...@tempa{#3}{#4}
> }
> \makeatother
> 
> \begin{document}
> \newfontfamily\foo{Times New Roman}
> \setmainfont{Helvetica}
> test: \IsFont{Times New Roman}{Times}{not Times}
> \par\foo
> test: \IsFont{Times New Roman}{Times}{not Times}
> \end{document}
> 
> 
> I've considered adding such code to fontspec before. But this interface
> is not very reliable -- font options must be exactly the same for two
> fonts to be "equal". See how you go, though.
> 
> Will

Thanks for this, Will. This is exactly the kind of thing I wanted. I
could use it to create a usable command that will 'fix' all subsequent
instances of the font. If it's designed as a command for an end user,
then the user can specify the exact set options.

I think that this might be easier than defining a new fontspec option to
fix a font, which would require redefining fontspec.

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] If font under fontspec

[Gareth Hughes]

Peter Dyballa wrote:
> 
> Am 20.09.2010 um 20:44 schrieb Gareth Hughes:
> 
>> I'm asking for a more useful implementation that checks whether a
>> certain font is in use now
> 
> 
> Wouldn't it be sufficient to check what \{rm,sf,tt}default are set to?

Perhaps, but a more general, fontspec solution is needed because the
fonts I want to work with are Syriac fonts. Also, I need to activate
kerning corrections only when that font is in use, i.e. it would be no
good to see if the font is being used in a document and then apply the
kerning corrections for all fonts in the document.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] If font under fontspec

[Gareth Hughes]

Alan Munn wrote:
> On Sep 20, 2010, at 1:30 PM, Gareth Hughes wrote:
> 
>> Dear friends,
>>
>> What is the best way to write a code that will check if a certain named
>> font, or group of fonts, is being used and implement some code if it is
>> the case? I mainly want to use this to make a few tweaks to proprietary
>> fonts, mostly kerning.
>>
> I recently asked the same question here and got a bunch of responses,
> many more than I thought my simple question would elicit:
> 
> <http://www.mail-archive.com/xetex@tug.org/msg01699.html>

Some bits of the code in that conversation are interesting, but I'm
asking for a more useful implementation that checks whether a certain
font is in use now, not just whether it might be available to XeTeX.
This is because the kerning tweaks should only be implemented when the
font that needs them is being used.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] If font under fontspec

[Gareth Hughes]

Dear friends,

What is the best way to write a code that will check if a certain named
font, or group of fonts, is being used and implement some code if it is
the case? I mainly want to use this to make a few tweaks to proprietary
fonts, mostly kerning.

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Multiple citation styles in a single document

[Gareth Hughes]

Gerrit Glabbart wrote:
> Am 20.09.2010 um 18:25 schrieb Gareth Hughes:
> 
>> Gerrit Glabbart wrote:
>>> Am 20.09.2010 um 16:57 schrieb Gareth Hughes:
>>> 
>>>> Seeing as the printing of the language name is part of the
>>>> style, you could write a simple style file that copies the
>>>> standard style you want to use, but alters the printing of
>>>> language names. This would allow BibLaTeX to use the language
>>>> field without printing it.
>>>> 
>>> I believe that’s what the »hyphenation« field is for (p. 23 in
>>> the biblatex manual). (A small number of) European languages
>>> only, for the time being, but still.
>> I think that only loads hyphenation patterns, but does not wrap the
>>  entry in a language environment or select bibliographical style
>> variants based on the language.
> 
>> From the manual: »This information may be used to switch
>> hyphenation patterns *and localize strings in the bibliography*.«
>> Also peruse the options on page 41, namely ›clearlang‹ and ›babel‹.
>> ›babel=other‹ will enclose the entry in an otherlanguage
>> environment.
> 
> So, »editor« becomes »Herausgeber« in German, for instance, ›pp.‹
> becomes ›S.‹ and so forth. I’m not sure what you mean by
> ›bibliographical style variants based on the language‹; surely, the
> bibliography should be as consistent as possible?

I didn't realise that that field operated on localisation strings too.
That's good news. However, I don't believe that it is able to change
inner quotes (seeing as outer quotes should be of the bibliography
language), or punctuation. In English, we write :  or
. , but, in French, we write  : . Can
this be controlled by use of the hyphenation field?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Multiple citation styles in a single document

[Gareth Hughes]

Gerrit Glabbart wrote:
> Am 20.09.2010 um 16:57 schrieb Gareth Hughes:
> 
>> Seeing as the printing of the language name is part of the style,
>> you could write a simple style file that copies the standard style
>> you want to use, but alters the printing of language names. This
>> would allow BibLaTeX to use the language field without printing it.
>> 
> 
> I believe that’s what the »hyphenation« field is for (p. 23 in the
> biblatex manual). (A small number of) European languages only, for
> the time being, but still.

I think that only loads hyphenation patterns, but does not wrap the
entry in a language environment or select bibliographical style variants
based on the language.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Multiple citation styles in a single document

[Gareth Hughes]

Pierre Morel wrote:
> Thank you, the switch from natbib to biblatex is (almost) painless !
> 
> I found how to remove URL fields and DOI fields from the bibliography
> (url=false,doi=false), but I'm still annoyed by the language field (I
> get "eng.", "ENG." or "English" between the titles and the journals,
> which is useless for me) and by the "in:" before the journal in which
> the article was published. Any idea on how to remove those ?

I've been using BibLaTeX. It's the best bibliographical solution for
multilingual documents in LaTeX, but I realise that it's not quite there
yet. The language handling is a bit limited, and, yes, the standard
styles print the name of the language in the entry (which looks very
amateur even in primary school!). That's only useful if you have a
translator, and the style adds 'trans. by N M from L'. Though try
getting it to use the word 'Arabic' and it goes a little nuts.

Seeing as the printing of the language name is part of the style, you
could write a simple style file that copies the standard style you want
to use, but alters the printing of language names. This would allow
BibLaTeX to use the language field without printing it. There are other
BibLaTeX styles bundled with TeX Live. I don't know if any of these have
already implemented better handling of the language field. Perhaps
'humanities'. It looks good on other things.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Kashida environment

[Gareth Hughes]

Fr. Michael Gilmary wrote:
> Fr. Michael Gilmary wrote:
> 
>> Well, I think I've got an environment for kashida. Please test it out
>> and change whatever is necessary. It seems to work here with the
>> attached example. Please note that I am no programmer and know very
>> little of the TeX or XeTeX internals. I got lucky with modifying just
>> a couple things from Jonathan's code. 
> 
> 
> It seems to me that, if others think this is useful, then maybe it
> should be included as an environment option in polyglossia (it seems
> pointless in shorter runs of text, no?) rather than a separate package
> --- since I can't imagine how to use it independently of polyglossia and
> friends (fontspec, bidi, etc).
> 
> Certainly, if desired, other glyphs could be mapped for Urdu, etc, as
> the present maps only include Arabic, Farsi and Syriac. However, I'm
> completely ignorant of what those glyphs would be since I know nothing
> of those languages.
> 
> Possible use in polyglossia:
> 
> In the preamble:
> 
> \setotherlanguages{syriac, farsi, arabic} % or whatever else
> 
> %% and define some appropriate font(s)
> 
> \begin{syriac_or_Arabic_or_farsi}[kashida]
> insert text here
> \end{syriac_or_Arabic_or_farsi}
> 
> Any thoughts, François?

Fr Michael, thank you for the environment version of kashida. I couldn't
work out how to do it, but that makes sense now.

I think the inclusion of this in Polyglossia makes sense. I'm slowly
writing a Syriac package, and have included it in that at the moment.
However, if kashida is multilingual, it should be in Polyglossia. The
only question I have is whether we might want to split kashida into
different script versions in the future.

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 275134


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Problem with Polyglossia's \aemph command

[Gareth Hughes]

Vafa Khalighi wrote:
>> On the attached minimal example I get the following error when I use the
>> Polyglossia command \aemph to place an overline over text.
>>
>>> * ! Undefined control sequence.
>> *>* \aemph #1->$\overline {\hboxR
>> *>*   {#1}}$
>> *>* l.6 ܗܢܐ ܛܣܛ: \aemph{ܫܠܡܐ}
>> *>*
>> *>* The control sequence at the end of the top line
>> *>* of your error message was never \def'ed. If you have
>> *>* misspelled it (e.g., `\hobx'), type `I' and the correct
>> *>* spelling (e.g., `I\hbox'). Otherwise just continue,
>> *>* and I'll forget about whatever was undefined.
>> *>*
>> *>* Missing character: There is no ܫ in font cmmi10!
>> *>* Missing character: There is no ܠ in font cmmi10!
>> *>* Missing character: There is no ܡ in font cmmi10!
>> *>* Missing character: There is no ܐ in font cmmi10!
>> *
>> Why can't I get this work?
>>
>> The control sequence \hboxR is undefined which means you have an old
> version of the bidi package. Update your bidi to the latest version
> (v1.1.4c).

Thanks, Vafa, bidi has changed so quickly that I had an old version left
on my local tree that I'd overlooked. As soon as that was deleted,
everything worked fine. Reminder to self: clean up TeX tree more often.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Problem with Polyglossia's \aemph command

[Gareth Hughes]

On the attached minimal example I get the following error when I use the
Polyglossia command \aemph to place an overline over text.

> ! Undefined control sequence.
> \aemph #1->$\overline {\hboxR 
>   {#1}}$
> l.6 ܗܢܐ ܛܣܛ: \aemph{ܫܠܡܐ}
>
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
> 
> Missing character: There is no ܫ in font cmmi10!
> Missing character: There is no ܠ in font cmmi10!
> Missing character: There is no ܡ in font cmmi10!
> Missing character: There is no ܐ in font cmmi10!

Why can't I get this work?

Gareth.
\documentclass{minimal}
\usepackage{polyglossia}
\setmainlanguage{syriac}
\setmainfont[Script=Syriac]{East Syriac Adiabene}
\begin{document}
ܗܢܐ ܛܣܛ: \aemph{ܫܠܡܐ}
\end{document}


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Separate fonts for Latin and Greek with fontspec?

[Gareth Hughes]

Fr. Michael Gilmary wrote:
> I don't know if this is useful or not ... a little code from Jonathan to
> assist with "kashida" --- he maps ranges of Unicode points to classes.
> Is this what you've done, Mike? I haven't looked yet at your
> ucharclasses, but will soon (I'm on breakfast clean up in 5 minutes!).
> 
> Here's the code.

I've been using that version of kashida.sty with Syriac definitions for
some time now. Are there any plans to make it an official CTAN package,
or part of one? Does Vafa's bidipoem package use a similar code? I can't
quite figure that out.

Quickly, once kashida.sty has been loaded, is there an easy way to turn
this feature on and off?

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 275134


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Separate fonts for Latin and Greek with fontspec?

[Gareth Hughes]

David Cottenden wrote:
> Sorry if I missed this in the manual, but is it possible to use fontspec
> to map most unicode characters to one font, and some to another? In
> particular, my intended use is that I prefer the Latin characters in
> Adobe Garamond Pro to those in Myriad Pro, but the latter has Greek
> support whilst the former does not, and they're similar enough that with
> the odd Greek character (which is all I use!) they are pretty
> stylistically compatible. Is it possible to set things up so that Greek
> appears in Minion and Latin (and everything else) appears in Garamond?
> 
> (I only ask the question since something like this is possible in
> unicode-math, IIRC.)

The fontwrap package can do this in PerlTeX. I still tend to use the
command sequences from Polyglossia when switching between scripts/languages.

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 275134


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Polyglossia and BibLaTeX

[Gareth Hughes]

Simon Spiegel wrote:
> I cannot really help you here, but you might be pleased to hear that
> François Charette, the author of polyglossia, is also one of the guys
> behind biber (http://biblatex-biber.sourceforge.net/ ). Biber is
> meant to replace bibtex (the program) for biblatex. So you can be
> assured that the biblatex people are quite aware of the problems of
> multingual bibliographies (multiscript support is also on the
> roadmap:
> https://sourceforge.net/apps/mediawiki/biblatex/index.php?title=Roadmap
> ).

Thanks for this information. It looks like I'll have to get Biber working.

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 275134


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Polyglossia and BibLaTeX

[Gareth Hughes]

Joachim Trinkwitz wrote:
> Hi Gareth,

Thank you for this reply, Joachim.

> Well, it looks like that by now there are not so many XeTeX users who
> know about the advantages of biblatex in comparison to the normal
> bibtex facilities in LaTeX or the numerous other bibtex related
> packages.

With talk of documentation in the air, a XeTeX way to handle with
bibliographies is clearly something that needs to be documented.

> According to the excellent biblatex manual, there are two bibtex
> entry fields who could help you with hyphenation problems: 'language'
> and 'hyphenation'. Have you tried these? If polyglossia manages to
> pretend being babel for biblatex, this should work.

The BibLaTeX manual is good, but there are some things that aren't
clear, like "Languages may be specified literally or as localization
keys. If localization keys are used, the prefix 'lang' is omissible".
I'm not entirely sure what that means. One problem might be that
BibLaTeX handles only a small number of Latin-script languages. It is
not clear how the preamble options 'language' and 'babel' and the entry
fields 'language' and 'hyphenation', and what Polyglossia might be doing
behind the scenes.

> But it would be best to contact Philipp Lehmann, the maintainer of
> biblatex, and urge him to implement polyglossia as a second language
> interface.

I've spoken with him on comp.text.tex, but that's probably not the best
place to have a conversation about this.

Thanks,

Gareth.

-- 
Gareth Hughes
Doctoral candidate in Syriac studies

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 275134


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Polyglossia and BibLaTeX

[Gareth Hughes]

Dear friends,

I regularly use BibLaTeX to manage citations and bibliographies.
Unfortunately, there's nothing in the either the BibLaTeX or Polyglossia
manuals about how to manage multilingual bibliographies. They work fine
together, but I'd like to be able to do some fine tuning.

It looks like Polyglossia does its trick of pretending to Babel for
BibLaTeX, but does it just set the default language? One problem I have
is with hyphenation of non-English titles in an otherwise
English-language bibliography. Can I use the babel=hyphen environment,
or do I need to wrap titles in my .bib file in \textgerman{} for instance?

When I try backend=biber my .aux file fails to point to my .bib file.
The .bib file is UTF8 encoded.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] wspr's realscripts & updated xelatex templates

[Gareth Hughes]

Philipp Stephani wrote:
> xltxtra is obsolete, the rest seems fine.

Now that fontspec does most of the stuff that xltxtra used to do, is it
only worth loading xltxtra if you want logos? Or are there other things
for which it's still needed?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] XeTeX documentation "initiative"

[Gareth Hughes]

David Perry wrote:
> 
> 
> On 9/11/2010 3:40 PM, Gareth Hughes wrote:
>>
>> I've become a bit of an evangelist for XeLaTeX in my discipline, but I
>> don't know of any straightforward manual that tells a complete novice
>> how to install the necessary TeX software and other tools on different
>> platforms. A no-assumptions introduction is hard to come by.
> 
> Did you ever see my tutorial at http://scholarsfonts.net/xetextt.pdf ?
> It may do much (not quite all) of what you are looking for, and it can
> be expanded if necessary.
> 
> David

Yes, and I see you've updated it a lot since I last looked at it. Thanks
for this. I think I might be able to make good use of it, as a means of
encouraging others to give XeLaTeX a go.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] XeTeX documentation "initiative"

[Gareth Hughes]

David Perry wrote:
> 
> 
> On 9/10/2010 12:18 PM, Tobias Schoel wrote:
> 
>> When someone arrives at xelatex he has usually gone some way through the
>> tex/latex world already. (Mostly latex, I think.) You can safely suppose
>> that he has read and used:
>> - lshort
>> - one latex book (companion, texbook, ...)
>> - some further tutorials and package documentations he needed
> Perhaps I am the exception, but I never used TeX until recently because
> my work requires Unicode and OT/AAT support for both linguistic and
> high-quality typesetting purposes.  That also means I need fonts that
> LaTeX traditionally knows nothing about, so the ability to use any
> system font is also important.  I was delighted when I discovered
> Xe(La)TeX but had a long learning curve ahead of me.
> 
> On Windows, support for advanced typography, including things like
> stylistic alternates that can be important to scholars, typically
> requires a large financial outlay for programs like InDesign.  I suspect
> there are a number of folks who could make good use of Xe(La)TeX but
> don't have the background that Tobias suggests.  Let's not forget them.
> 
> David

Hear, hear, David! TeX and LaTeX are dominated by scientists because
they are more accessible to people who think naturally in programming
terms and like the TeX way of managing formulae and graphics. However,
XeTeX has a strong appeal to people working in different languages,
especially those that require bidirectionality or complex text layout.
Most of us coming from this angle have little or no previous TeX
experience, and thus need quite different things from the manuals.

I've become a bit of an evangelist for XeLaTeX in my discipline, but I
don't know of any straightforward manual that tells a complete novice
how to install the necessary TeX software and other tools on different
platforms. A no-assumptions introduction is hard to come by.

I would be happy to help with the writing.

Has anyone thought of setting up a wiki for collaborative editing and
for keeping everything up to date?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] using different fonts for one language (Syriac)

[Gareth Hughes]

Philip Taylor (Webmaster, Ret'd) wrote:
> Many thanks for the explanation and clarification, Gareth.
>
> If I have offended anyone by referring to 'Nestorian' or 'Jacobite'
> in this context, I sincerely apologise : I was using the terms used
> by Daniels and Bright, whom I had (perhaps mistakenly) assumed
> would be cautious in their use of potentially pejorative terms.

Sorry, Phil, it's not really offensive to use these terms, seeing as the
terms are still used often in literature. The standard books on Syriac,
many of which are a little dated, still use these terms, so those who
aren't specialists in the field tend to pick them up. The terms are
political-theological slurs used against those who wrote with these
scripts, labelling them as the followers of either Nestorius or Jacob
Baradaeus, rather than communities with their own identity and long
history. That's why we tend to use the names used by users of the
scripts today.

I hope that helps,

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] using different fonts for one language (Syriac)

[Gareth Hughes]

Philip Taylor (Webmaster, Ret'd) wrote:
> I'm way out of my depth here, but looking at the entry for Syriac
> in Daniels & Bright;s "The World's Writing Systems" is seems to
> me that it would be a major deviation from the intended and
> apparent meaning  of \ttfamily, \slfamily or \itshape
> if one were to try to use them for switching between Estrangelo,
> Serto, Nestorian & Jacobite.  Are there no more better hooks
> that can be used for switching between related scripts that do
> not fall into the categories that Ulrike proposes ?

I agree with you that these categories that are logical to Latin
typefaces, and can be extended to Greek and Cyrillic, are less than
helpful in describing other scripts. Yes, we are faced with the
awfulness of 'italic' Arabic and Syriac, which is little more than an
ugly borrowing from Latin faces. These scripts have their own ways to
give emphasis. We don't use the names 'Nestorian' or 'Jacobite' to refer
to script styles in Syriac, as they are derogatory. Even so, many books
continue this use. We use 'Estrangela/o' to refer to the classical
script, 'Serto' to refer to western script and 'Madnha' to refer to
eastern script. That said, I've seen manuscripts use mixtures of these
styles in the same work, even within the same word!

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] using different fonts for one language (Syriac)

[Gareth Hughes]

Dear Adam,

I've been thinking of writing a XeLaTeX package for Syriac that would
deal with this and other issues.

I would choose one Syriac font as my main Syriac font (Serto in your
case), and others as exceptions. Then use polyglossia to set up the main
Syriac font, thus:

\usepackage{polyglossia}
\setmainlanguage{syriac}% or use \setotherlanguage if your main language
is something other.
\newfontfamily\syriacfont[Script=Syriac]{Serto Jerusalem}

Then you need some code to set up Estrangelo:

\newfontfamily\estrangelofont[Script=Syriac]{Estrangelo Edessa}
\newcommand{\textestrangelo}[1]{\textsyriac{\estrangelofont #1}}
\newenvironment{estrangelo}{\begin{syriac}\estrangelofont}{\end{syriac}}

Now, you have a command, \textestrangelo{ܫܠܡܐ}, that will render
Estrangelo text, and an environment,
\begin{estrangelo}...\end{estrangelo}, for longer pieces of text.

Have fun,

Gareth.

Adam McCollum wrote:
> Dear list members,
> 
> I'm working on a document with Syriac text and I need to use two
> different fonts. As some of you probably know, there are three different
> scripts used for Syriac; I am mostly using Serto, but I also need to put
> a few things in Estrangela. I suppose there is a way to do this, but I
> don't know what it is.
> 
> Thanks in advance for any help!
> 
> Adam McCollum


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] XeTeX documentation? (from "Checking if a font exists")

[Gareth Hughes]

Peter Baker wrote:
>  On 8/31/10 6:51 AM, Vafa Khalighi wrote:
>> I believe that in any case the original developer should write the
>> main documentation not anyone else simply because the original
>> developer implemented the software and he knows absolutely every
>> single detail about his software and what he has implemented.
> 
> But developers are not always good writers. Our Will Robertson has
> produced a great manual for fontspec, but some TeX developers who have
> written manuals would have done better to recruit someone else to do it
> for them. A developer's duty is to write well commented code, and to be
> willing to work with writers of documentation to help them get it right.

There has always been the RTFM response to questions about some code or
other. Yes, there are people who find it easier to post to a discussion
group than read the manual. One problem with TeX is that one might be
reading the wrong manual, because one is blaming the wrong package.
However, if there is a steady stream of questions from users who have
read the right manual but still implement the package wrongly, then the
manual is either not clear enough or has holes in its coverage. However,
rather than taking over the manual, I think it would be far better if
developers felt able to ask for input from others on how best to improve
the manual. After all, I'm sure the developer doesn't have to read their
own manual, but the rest of us do.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ancient Hebrew font problem

[Gareth Hughes]

Karljurgen Feuerherm wrote:
> Hi
> 
> As I do some Hebrew, and have just migrated to a Mac (last month), I am
> curious why the font feature need not be declared on a Mac?
> 
> Thanks
> 
> KF

The fontspec manual discusses the difference between ICU and AAT font
handling. Macs use the latter, Linux and other operating systems use the
former. With ICU handling, language and script features have to be
selected manually, whereas they are automatic in AAT. In fontspec, if
you select language and script options, ICU handling will be activated.
If you do this on a Mac, it could well look messy. This list often sees
posts where people with Macs have selected language or script tags and
it has caused problems, or when users of other OSs don't select these
tags. I'm sure someone with more technical knowledge could tell us more
about this issue if necessary.

Gareth.
> 
>>>> On Mon, Aug 23, 2010 at  4:02 PM, in message
> <4c72d3dd.8000...@gmail.com>,
> Gareth Hughes  wrote: 
>> Carsten Ziegert wrote:
>>> Hi,
>>>
>>> I am facing a problems with hebrew vowels while trying three
> different
>>> fonts (see example file):
>>>
>>> With SBL Hebrew and Ezra SIL, the vowels are too much on the left
> under
>>> the consonants.
>>> Cardo seems ok, except for shureq (leftmost letter of the third and
>>> fourth word from the left). The point is on the right hand side of
> the
>>> Waw consonant instead of on the left.
>>>
>>> System specs: Ubuntu Karmic, fontspec 2010/08/01 v2.0c,
>>> XeTeXk, Version 3.141592-2.2-0.996-patch2 (Web2C 7.5.6)
>>>
>>> What can I do to achieve the correct vowel adjustment? Does anyone
> have
>>> experiences with fonts for Biblical Hebrew?
>>>
>>> Thanks,
>>> Carsten
>> Dear Carsten,
>>
>> The problem arises from not telling fontspec you're writing in
> Hebrew:
>> you need to declare the font feature Script=Hebrew (you wouldn't
> need
>> this on a Mac). To do this you need the format
>> \fontspec[Script=Hebrew]{Ezra SIL} or whatever font you desire.
>>
>> Are you using that format for a reason? I would prefer to use
>> polyglossia for a bilingual document:
>>
>> \usepackage{xltxtra, polyglossia}
>> \setmainlanguage{english}
>> \setotherlanguage{hebrew}
>> \newfontfamily\hebrewfont[Script=Hebrew]{Ezra SIL}
>>
>> \begin{document}
>> Ezra SIL: \texthebrew{וְהָאָ֗רֶץ הָיְתָ֥ה תֹ֨ה֙ וָבֹ֔ה}
>> \end{document}
>>
>> Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ancient Hebrew font problem

[Gareth Hughes]

Kirk Lowery wrote:
> On Mon, Aug 23, 2010 at 4:02 PM, Gareth Hughes  wrote:
> 
>> Are you using that format for a reason? I would prefer to use
>> polyglossia for a bilingual document:
>>
> 
> Two (possibly related questions):
> 
> 1. Does polyglossia preclude the need for the bidi package?

Polyglossia loads bidi if an RTL language is defined.

> 2. What advantages does polyglossia have for bilingual documents?

Polyglossia provides logical, clean commands like \texthebrew{}, which
will change font and set direction. It does quite a few other things too
like set page numbers, caption names and date formats for the overall
document language. I've written bilingual documents in XeLaTeX before
polyglossia and find it a lot easier with it.
> 
> Thanks!
> 
> Kirk

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ancient Hebrew font problem

[Gareth Hughes]

Carsten Ziegert wrote:
> Hi,
> 
> I am facing a problems with hebrew vowels while trying three different
> fonts (see example file):
> 
> With SBL Hebrew and Ezra SIL, the vowels are too much on the left under
> the consonants.
> Cardo seems ok, except for shureq (leftmost letter of the third and
> fourth word from the left). The point is on the right hand side of the
> Waw consonant instead of on the left.
> 
> System specs: Ubuntu Karmic, fontspec 2010/08/01 v2.0c,
> XeTeXk, Version 3.141592-2.2-0.996-patch2 (Web2C 7.5.6)
> 
> What can I do to achieve the correct vowel adjustment? Does anyone have
> experiences with fonts for Biblical Hebrew?
> 
> Thanks,
> Carsten

Dear Carsten,

The problem arises from not telling fontspec you're writing in Hebrew:
you need to declare the font feature Script=Hebrew (you wouldn't need
this on a Mac). To do this you need the format
\fontspec[Script=Hebrew]{Ezra SIL} or whatever font you desire.

Are you using that format for a reason? I would prefer to use
polyglossia for a bilingual document:

\usepackage{xltxtra, polyglossia}
\setmainlanguage{english}
\setotherlanguage{hebrew}
\newfontfamily\hebrewfont[Script=Hebrew]{Ezra SIL}

\begin{document}
Ezra SIL: \texthebrew{וְהָאָ֗רֶץ הָיְתָ֥ה תֹ֨הוּ֙ וָבֹ֔הוּ}
\end{document}

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Iranian Youth Festival (about bidi and xepersian)

[Gareth Hughes]

Vafa Khalighi wrote:
> Several month ago, I participated in the "Invention" section of Iranian
> Youth Festival and one of my three projects was bidi and xepersian. I got
> the second best prize in this competition in "Invention" section. I just
> would like to thank the xetex community, Jonathan Kew, Will Robertson, Ross
> Moore, Mehdi Omidali, François Charette, Karl Berry and a lot of other
> people for their help and motivations.
> 
> Original (In Persian): http://www.bornanews.ir/vgldkf0o.yt0ofyl22fa6y.h.html
> 
> English Translation:
> http://translate.google.com/translate?hl=en&sl=fa&u=http://www.bornanews.ir/vgldkf0o.yt0ofyl22fa6y.h.html&prev=/search%3Fq%3D%D9%88%D9%81%D8%A7+%D8%AE%D9%84%DB%8C%D9%82%DB%8C+%D9%85%D8%AE%D8%AA%D8%B1%D8%B9+%D9%88+%D9%85%D8%A8%D8%AA%DA%A9%D8%B1&rurl=translate.google.com.au


Congratulations, Vafa! It's good to hear you're getting recognition for
your work.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ligatures and searching in PDFs

[Gareth Hughes]

David J. Perry wrote:
> I am curious; are you using standard Unicode Syriac fonts?  In such
> fonts, there is no need for, nor should there be, PUA assignments for
> the joined shapes.  (And any font whose maker puts joined shapes
> "somewhere that's going to spare" needs to go back to Unicode 101 and
> learn some good practices.  There is no such place in Unicode and
> putting one's private characters in codepoints marked reserved or used
> for other scripts is really bad.)  I just looked at the Estrangelo
> Edessa font and it (correctly) has no PUA assignments for other than the
> isolated shapes.  (If you are using older fonts, created before Syriac
> was supported in Unicode, of course there will be all sorts of
> nonstandard things.  But we can't use those to judge whether XeTeX is
> doing the right thing.)
> 
> Another fundamental question is whether Adobe even claims that rtl or
> mixed directional text can be searched or copied correctly from a PDF. 
> I did some googling on RTL support in PDFs and didn't really find an
> answer.  But the overall support for RTL in PDF seems pretty spotty,
> which is perhaps not surprising given Adobe's track record with RTL in
> other products such as InDesign.  So the non-searchable PDFs may not be
> the fault of XeTeX.  If you or anyone else knows the answer, please let
> us know--I agree with you completely that it is an important issue.
> 
> David

Thanks, David.

In Estrangelo Edessa the joined glyphs are 'unmapped' (don't have
Unicode code points). So, is it that they are unmapped that makes them
unsearchable or that PDFs baulk at RTL scripts? Some Latin ligatures
have Unicode code points at U+FB00-6. The Unicode blocks Arabic
Presentation Forms-A and -B provide the joined forms for Arabic-based
scripts, so it can be searched and copied from a PDF (although when
pasted I get the isolated forms separated by spaces, which is still
better than copying the raw joining glyphs). This would suggest that a
similar thing would be possible for Syriac too, but, like a 'Th'
ligature, would we need to have explicit Unicode code points for
these to work properly? For starters, how much is possible within XeTeX,
and how much would require mass lobbying of Adobe or the Unicode
Consortium to make it work?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ligatures and searching in PDFs

[Gareth Hughes]

Ross Moore wrote:
> However, PDF has two separate mechanisms to overcome this.
> 
>  1.  a CMap resource for the font
>  2.  the /ActualText  tagging construction
> 
> Concerning method 1.  CMap resources:
> 
> I don't know where that CMap resource is being constructed.
> Presumably it is by  xdvipdfmx  as it subsets the font
> for inclusion. Presumably it is getting information from
> the complete font itself.
> Is there a way to override some entries and get those
> ligatures pointing to letter combinations?
> Again, I don't know. Maybe someone else can comment.
> 
> Concerning method 2.  /ActualText tagging:
> 
> Here is an example document that demonstrates how it
>  a.  does work with pdfTeX
> but
>  b. produces broken PDFs with XeTeX + xdvipdfmx .
> 
> When processed by XeTeX this file produces a PDF that is readable
> in both Apple's Preview, and in Adobe Reader and Acrobat Pro.
> 
> However, Acrobat Pro reports the content stream to be mal-formed.
> In neither case, using XeTeX, does  Copy/Paste respect the  /ActualText .
> 
> So my conclusion is that  xdvipdfmx  does not provide the method
> to put tagging directly into the content stream, thereby allowing
> /ActualText --- and other forms of tagging --- to be used.
> 
> pdfTeX, on the other hand, does allow this to some extent.
> That is, /ActualText works in some situations.
> Other kinds of tagging are more delicate, requiring an especially
> modified version of pdfTeX having extra primitives.
> 
> I gave a talk at the TUG 2009 meeting on this last year,
> and will be giving another at TUG 2010 in a few weeks from now.
> 
> You are not mistaken in that XeTeX cannot use /ActualText
> at present --- unless there have been some recent developments
> to  XeTeX  or  xdvipdfmx  of which I am not aware.
> (That's quite possibly the case.)

Obviously, it is important that we are able to produce PDFs that are
searchable and allow us to copy and paste plain text from them. We could
just try to use 'safe' ligatures, but that's not the point either.

What is more, I do a lot of work with Syriac, a cursive script for which
most joined shapes are encoded in the PUA or somewhere that's going
spare. This means that my XeTeX PDFs aren't searchable or copyable in
Syriac. Only one or two Syriac letters per word can be searched or copied.

Is it felt that this issue is a priority for the future development of
XeTeX? I feel that given XeTeX's speciality in working with Unicode and
OpenType this is an important issue.

Gareth.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Ligatures and searching in PDFs

[Gareth Hughes]

Andy Lin wrote:
> In order to make the common f/ff ligatures searchable in PDFs, add the
> following lines and compile the map file with teckit_compile (should
> be in the bin folder):
> U+0066 U+0066 <>  U+FB00  ; ff -> ff ligature
> U+0066 U+0069 <>  U+FB01  ; fi -> fi ligature
> U+0066 U+006C <>  U+FB02  ; fl -> fl ligature
> U+0066 U+0066 U+0069  <>  U+FB03  ; ffi -> ffi ligature
> U+0066 U+0066 U+006C  <>  U+FB04  ; ffl -> ffl ligature
> 
> I've attached such a map file and the resulting tec file for those who
> aren't interested in the nitty-gritty. Simply drop these into the
> fonts\misc\xetex\fontmapping folder and run texhash/mktexlsr.

I had noticed that the ligatures 'ch' and 'Th' are not searchable in
Linux Libertine. I added the following mappings:
U+0063 U+0068   <>  U+E03B  ; ch -> ch ligature
U+0054 U+0068   <>  U+E049  ; Th -> Th ligature
But these do not make it possible to search or copy/paste as uncompiled.
The .tec file is compiled correctly and XeTeX finds it. Any thoughts?

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] XMP and XeTeX

[Gareth Hughes]

Dear friends,

A few people have been asking about tagging PDFs with XMP metadata.
Currently, this seems not to be all that straightforward with XeTeX.
There are a couple of packages that assist with the task under PDFTeX:
hyperxmp and xmpincl. Of these, I think hyperxmp is the more elegant, as
it doesn't require the user creation of a separate file for the
metadata, but gleans it from the PDF strings passed to hyperref.

I've had a message back from Scott Pakin, who created and manages
hyperxmp, who believes that it would be possible to get hyperxmp working
from XeTeX, but only so that the XMP tags would be visible to PDF-aware
readers. To be able to make XMP tags available to generic XMP metadata
displayers, there would have to be a way to allow xdvipdfmx to generate
an uncompressed and unencoded PDF stream.

I think it might be useful for hyperxmp to be able to work with XeTeX,
but, if it's only making metadata available to PDF readers, it is doing
little more than hyperref already does (except it would encode copyright
licensing material for the document). Further than this, what do the
more technically minded among us think about the possibility, or lack
thereof, of more fundamental support for XMP metadata?

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Bidipoem

[Gareth Hughes]

Vafa Khalighi wrote:
> Hi Gareth

Hi Vafa!

> the bidipoem package is indeed intended for typesetting modern and
> traditional Persian poems and may not be suitable for typesetting poems in
> other scripts.

Perhaps, if I were to typeset the Touma Audo's famous Syriac translation
of the Ruba'iyat of Omar Khayyam, you might have mercy on my persistent
misuse of your code!

> I think that I have not understood your problem correctly and I do not know
> how I should typeset Syriac with xetex.fontspec complained about every
> single font that I used to test that it does not contain  Syriac script.
> Could you please send a minimal example and what font should I use for this
> script?

I've attached the input and output minimal files; they use Estrangelo
Edessa, which is a freely available Meltho Font from Beth Mardutho.

> If you typeset a line (which is just one line in comparison to the line
> before that contained two halves and there was a gap between them), then
> this line is aligned at the center of previous line and this is a feature of
> traditional Persian poems. What I meant is:
> 
> xxxx
> 
>  xxx
> 
> Now if you have several of these (single lines), they are aligned with
> respect to each other (their beginning starts at one horizontal width and
> their endings also ends at one horizontal width) so you have something like:
> 
> xxxx
> 
>  xxx
> 
>  xxx
> 
> xxx
> 
> Now I do not understand how your example should look like. Could you please
> enlighten me and send a minimal example using only English alphabets?

Yes, I understand what the package does, that ever full line or half
line has the same width. However, I'm working with a verse form in which
the single lines are often longer than the half lines, so the half lines
look very stretched out. I was wanting to know if there's a way to treat
single lines as having double the width of half lines to prevent the
latter from being overstretched. I suppose it might look like:

xxxx
xxxx

xxxx
xxxx


> Thanks

Thank you,

Gareth.


bidipoemtest.pdf
Description: Adobe PDF document
\documentclass{minimal}
\usepackage{xltxtra, polyglossia, bidipoem, PersianKashida}
\renewcommand\poemcolsepskip{2em}
\setclass \A {710}
\setclass \R {0715,0717,0718,0721,0728,072A,072C}
\setclass \D {0712,0713,071A,071B,071D,071F}
\setclass \D {0722,0723,0725,0729,072B}
\setclass \L {0720}
\setclass \V {0730,0731,0732,0733,0734,0735}
\setclass \V {0736,0737,0738,0739,073A,073B,073C}
\setclass \V {073D,073E,073F,0740,0741,0742,0743}
\setclass \V {0744,0745,0746,0747,0748}
\setmainlanguage{syriac}
\setmainfont[Script=Syriac]{Estrangelo Edessa}
\begin{document}
\begin{traditionalpoem}
ܦܬܚ ܠܢ ܢܚܙܝܘܗܝ&ܐܦ ܢܗܠ ܒܗ\\
ܢܥܢܐ ܘܢܐܡܪ&ܕܐܝܟܘ ܚܝܠܟ\\
ܗܐ ܓܝܪ ܝܘܡ̈ܬܐ ܬܠܬܐ ܗܘܘ ܠܗ\\
ܘܢܐܡܪ ܠܗ ܐܘ ܬܠܝܬܝܐ&ܕܠܪܒܝܥܝܐ ܠܠܥܙܪ\\
ܐܚܝܐ ܐܚܐ ܠܩܢܘܡܟ&ܦܬܚ ܡܘܬܐ ܬܪ̈ܥܝܗ̇ ܕܫܝܘܠ\\
ܘܐܙܠܓ ܡܢܗ̇&ܙܝܘܐ ܕܦܪܨܘܦܗ ܕܡܪܢ\\
ܘܐܝܟ ܣܕܘܡ̈ܝܐ ܒܠܥܘ ܗܘܘ\\
ܡܫܘ ܘܒܥܘ ܬܪܥܗ̇ ܕܫܝܘܠ ܕܐܒܕ ܠܗ̇
\end{traditionalpoem}	
\end{document}


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Rubber support for xelatex

[Gareth Hughes]

Wilfred van Rooijen wrote:
> Hello all,
> 
> Apparently, a bugfix is available allowing one to use rubber with xelatex. 
> The required fix to rubber can be found here:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579757
> 
> Regards,
> Wilfred van Rooijen

That's so simple and beautiful. Thanks for posting.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Bidipoem

[Gareth Hughes]

Dear all, and especially وفا,

I'm using bidipoem's traditionalpoem environment to typeset a Syriac
madrasha. The metre of many madrashe mixes couplets, which are usually
set on a single line with a gap between the two halves, and single
lines. Traditional poem is great at setting the couplets, but how do I
mark up the single lines so that their ends match the two ends of the
couplets? Here's one stanza from the madrashe:

\begin{traditionalpoem}
ܦܬܚ ܠܢ ܢܚܙܝܘܗܝ&ܐܦ ܢܗܠ ܒܗ\\
ܢܥܢܐ ܘܢܐܡܪ&ܕܐܝܟܘ ܚܝܠܟ\\
ܗܐ ܓܝܪ ܝܘܡ̈ܬܐ ܬܠܬܐ ܗܘܘ ܠܗ\\
ܘܢܐܡܪ ܠܗ ܐܘ ܬܠܝܬܝܐ&ܕܠܪܒܝܥܝܐ ܠܠܥܙܪ\\
ܐܚܝܐ ܐܚܐ ܠܩܢܘܡܟ&ܦܬܚ ܡܘܬܐ ܬܪ̈ܥܝܗ̇ ܕܫܝܘܠ\\
ܘܐܙܠܓ ܡܢܗ̇&ܙܝܘܐ ܕܦܪܨܘܦܗ ܕܡܪܢ\\
ܘܐܝܟ ܣܕܘܡ̈ܝܐ ܒܠܥܘ ܗܘܘ\\
ܡܫܘ ܘܒܥܘ ܬܪܥܗ̇ ܕܫܝܘܠ ܕܐܒܕ ܠܗ̇
\end{traditionalpoem}

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] isolated Arabic letters in XeTeX

[Gareth Hughes]

Abdulrahman Al-Abdusalalm wrote:
> Hi,
> 
> After running the sample Arabic.tex through XeTeX (distro: TeXLive 2009
> under linux ubuntu)
> I got output pdf file with isolated arabic letters (i.e. ا ل ش ف ر ه)
> instead of connected ones.
> Am using the font Scheherazade.ttf (after ofcourse dropping to the correct
> place in TDS).
> I will appreciate any help ... thnks.

You need to tell XeTeX that to use Arabic script options in the font
table by using the option Script=Arabic in fontspec. If fontspec is
loaded, use:

\setmainfont[Script=Arabic]{Scheherazade}

if that's your main font. Because of different font technologies, Mac
users don't need to specify the script, but the rest of us do.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Arabic fonts and ligatures after migrating machine

[Gareth Hughes]

Manuel Souto Pico wrote:
> Dear all,
> 
> After migranting to a new machine and copying all files and installing
> Tex Live again, I find that when I try to typeset (in
> TexShop) some documents that I had in Arabic, ligatures stop working.
> I use Mac OS X 10.6.3.
> 
> The font I use is Scheherazade. I copied the file
> ScheherazadeRegAAT.ttf in /System/Library/Fonts (although it doesn't
> appear in the Font Book, I don't know why).
> 
> My minimal example is:
> 
> %!TEX TS-program = xelatex-xdvipdfmx
> %!TEX encoding = UTF-8 Unicode
> 
> \documentclass[a4paper]{article}
> \usepackage{polyglossia}
> \setmainlanguage{arabic}
> \setotherlanguage{galician}
> \newfontfamily\arabicfont[Scale=1.5,Script=Arabic]{Scheherazade}

Has anyone yet mentioned that the Script feature automatically selects
the ICU renderer? If you're on a Mac, you almost certainly want to use
AAT instead. Simply remove 'Script=Arabic'.

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] accented character ṛ within \section {ṛ}

[Gareth Hughes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

TIMOTHY P. LIGHTHISER wrote:
> Hi!
> 
> I use texlive/2009; TexShop 2.33; and 10.4.11.
> 
> I am also now using a font called Junicode (http://junicode.sourceforge.net).
> 
> When the accented character ṛ (-r- with an underdot) is input within
> \section{}, a box appears in the pdf rather than the character.
> 
> At the same time, however, this character does appear within the body
> of the text, as well as within the header.
> 
> A minimal example is below.
> 
> Thanks in advance for any help.
> 
> 
> %!TEX TS-program = xelatex
> %!TEX encoding = UTF-8 Unicode
> \documentclass[a4paper,10pt,draft,twoside]{book}
> \usepackage{xltxtra}
> \usepackage{lipsum}
> 
> \setmainfont[Mapping=tex-text]{Junicode}
> \defaultfontfeatures{Mapping=tex-text}
> 
> \begin{document}
> \tableofcontents
> 
> \chapter{Tṛtīyo 'dhyāyaḥ}
> Tṛtīyo 'dhyāyaḥ
> 
> \lipsum[1-8]
> 
> \end{document}

You could use fake bold just for this character. If you set the weight
correctly, it shouldn't look too out of place among the real bold
characters.

Gareth.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFL1cUK9UDttp8yrx4RAmZPAKC2wTRjixahH2sn3epYu1C2e1d9LQCeILK2
IOOjL9XfWZJOv/lMxniZ1Zo=
=suLi
-END PGP SIGNATURE-


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Strange ligature behaviour

[Gareth Hughes]

Over the last few weeks I've been noticing some strange behaviour in the
formation of ligatures in bold fonts (I don't think it's just restricted
to Libertine-Biolinum). I'm using TeX Live 2009 and have everything
up-to-date, and, somewhere in the update, thing went a little odd.
Ligatures started being replaced by white space or odd glyphs. I've
noticed this in Latin text and Malayalam, and also when updating old
XeTeX documents that displayed perfectly before, but now get all the
ligatures mangled. I wonder if anyone else has experienced this, or
knows what's up. I'll see if I can rustle up a minimal if that would help.

Thanks,

Gareth.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Lao typesetting in XeTeX

[Gareth Hughes]

Brian Wilson wrote:
> "Hello World"

Hello Brian!

> I'm a XeTeX Newbie who can read Thai, Lao and Khmer, with Lao being my first
> language of focus for XeTeX typesetting. I have two questions.
> 
> 1.  Where do I start? I have found several manuals for LaTeX, but when I
> compile a new document, the Lao fonts do not show.

Perhaps a brief example would help:

%
\documentclass{minimal}
\usepackage{fontspec}
\setmainfont[Script=Lao]{NameOfLaoFont}
\begin{document}
ອັກສອນລາວ
\end{document}
%

Replace 'NameOFLaoFont' with the human readable name of the font you
wish to use. The font should be installed as a system font on your
system. If the Lao font has OpenType tables, the 'Script=Lao' definition
is used to make sure that the correct substitutions and positionings are
used, for combining vowels etc.
> 
> 2. Tomorrow I will be going to Laos for other business and will take time to
> meet with the director of IT integration for the government who created the
> national font (yes, they have a national font). Is there any information
> that I should get from him that would help in my Lao XeTeX project?

The two watchwords here are Unicode and OpenType: that glyphs are in
their proper Unicode positions, and the font comes with those handy
OpenType tables.

> Thank you,
> 
> Brian Wilson

I hope this helps.

Gareth.

-- 
Gareth Hughes

Department of Eastern Christianity
Oriental Institute
Pusey Lane
Oxford
OX1 2LE

+44 (0)1865 615331


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Happy Persian New Year and Happy Nowruz

[Gareth Hughes]

Happy Nowruz, Vafa! I wish you and all XeTeXnicians:
Satisfaction
Sympathy
Support
Sanity
Sweetness
Security
and a
Spring in your step!

Gareth.

Vafa Khalighi wrote:
> Happy Persian new year and happy Nowruz. I wish a year full of happinesses
> and success for all of you.
> 
> http://en.wikipedia.org/wiki/Nowruz
> 
> 
> Best wishes,
> Vafa Khalighi
> 
> 
> 
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex