Thank you, Arthur! Everything works now. Last night I was banging my
head up against this and I knew I was making it harder than it was. I
really appreciate the flexibility that XeTeX offers in defining new
languages and in providing access to all OT features contained in a
font. It's a tremendous help to those of us who work to support
scholars of historic scripts/languages, for which implementation is slow
in coming (if it ever does) in commonly used word processors and
publishing programs.
David
On 9/21/2015 8:42 PM, Arthur Reutenauer wrote:
I'm sure I am not writing the
commands right, but without examples to follow I am lost and hope that
someone can help. Minimal example below.
Language and script are selected the same way as features, with the
keys Language and Script respectively. You thus have several commands
at your disposal, either (untested code)
\fontspec{FaliscanCDS}
\addfontfeatures{Script=Old Italic,Language=Faliscan}
or
\fontspec[Script=Old Italic,Language=Faliscan]{FaliscanCDS}
or -- the best choice in an actual document
\newfontfamily\olditalicfont[Script=Old
Italic,Language=Faliscan]{FaliscanCDS}
and use then \olditalicfont for your text in Faliscan.
These commands of course need the Faliscan language to be defined with
\newfontlanguage.
Best,
Arthur
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
