Hi Dominik, this is how I'm doing it. Hope it helps.
Best,
Alessandro
--
\documentclass{article}
\usepackage{polyglossia}
\setdefaultlanguage{english}
\setotherlanguage{sanskrit}
\defaultfontfeatures{Mapping=tex-text
the italics along:
\newcommand{\romskt}[1]{\textsanskrit{\emph{#1}}}
Cheers,
Alessanro
On 02/14/2017 03:00 PM, Dominik Wujastyk wrote:
Nice to see you here, Alessandro! Many thanks for your code. So it's
the \begin{sanskrit} that switches on the correct hyphenation. And the
string "devan
Hello everybody,
With the MinionPro font, if I try to typeset a localized
form(specifically, Serbian) of U+0431 CYRILLIC SMALL LETTER BE
preceded by U+0423 CYRILLIC CAPITAL LETTER U, Xe(La)Tex doesn't kern
it the right way, because it provides me with a blatant case of
characters stuck together.
That would be redundant since the Polyglossia package already takes care
of selecting alphabet language, thus also the relevant localized
glyphs if needed.
\usepackage{Polyglossia}
\setmainlanguage{Serbian}
However I tried to add:
\defaultfontfeatures{Language=Serbian, Script=Cyrillic,
Hy there,
My problem should stem from XeTeX's inability to read the GPOS (Glyph
Positioning Table) as in PangoView MinionPro's glyph positioning is OK.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Yeah, as I told you I'd taken a look in FontForge and it came out font
designers had anticipated such combination in the kerning pairs table.
In effect it works in PangoView but I can't figure out how to direct the
output toward a pdf, so I can't show you the right kerning, anyhow there
should be
OK, I got it know. Can you suggest me any workaround? This bug is very
annoying since the combination occurs frequently.
Thank you
Le samedi 05 février 2011 à 23:21 +0100, Adam Twardoch (List) a écrit :
Ps. Technically speaking, in OpenType, kerning moves the right
sidebearing of the first
Thank you, Peter. I tried but it's still far from being satisfying. Too
much on the right now. Looking on FontForge the kerning set by designers
for the combination of glyphs uni0423+uni0431.ital is -53. Previously
Peter reported a kerning value of -183. However, I don't know if the
units of
-2ex is OK, it looks remarkably like the output FontForge proposes.
To John: I don't think there should be copyright infringements, as I'm
modifying output, not the font per se. And what's more it's XeTeX that
gets it wrong, by apparently ignoring the *right* kerning set by font
designers. What
To Peter:
Yeah, it's -0.2ex, I made a typing error. Now, what about the
kerning=mykerns option that would allow me to set a standard paradigm
for this combination without having to look for add relevant
instructions ad infinitum?
Thank you
--
Ahem... not so easy! I looked for something more down-to-earth.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
force me to undergo the epic
effort of manually kerning the book.
Best wishes
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
to offer such an
option.
Thank you for helping me,
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
number sign:
n\textsuperscript{o}
I cannot use babel in this case for I need Classical Greek with a
Unicode font in my text, so I'm forced to rely on polyglossia and XeTeX.
So, back to my question:
Can footmisc be of use here?
--
Alessandro Ceschini
indentation
than normal ones.
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
?
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
.
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
So should it look like this:
\makeatletter
\newdimen\parindentFFN
\parindentFFN=10in
\renewcommand \@makefntext [1]%
{%
\leavevmode \hbox to \parindentFFN {}\@thefnmark.~#1%
}
\makeatother
It doesn't work, anyhow.
--
Alessandro
{%
\ifFBFrenchFootnotes
\@makefntextFB{#1}%
\else
\@makefntextORI{#1}%
\fi}%
}%
}
--
Alessandro Ceschini
}
\usepackage{enumitem}
\setenumerate{nolistsep}
\setitemize{nolistsep, label=$-$}
\usepackage{footmisc}
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
hyphenating patterns, one probably gets slightly better
results as far as traditional syllabic division of Sanskrit.
Best,
Alessandro Graheli
Il giorno 12/set/11, alle ore 12:58, Dominik Wujastyk ha scritto:
I've just had a stimulating conversation about this with my friend
and fellow Sanskritist
something to do with TeXWorks:
http://code.google.com/p/texworks/issues/detail?id=550#makechanges but
then they told me the SyncTeX code is to be blamed for that.
Greetings
--
/Alessandro Ceschini/
--
Subscriptions, Archive, and List information, etc
Le 31/10/2011 19:47, Alessandro Ceschini a écrit :
Hi
My problem is kind of complicated:
1. After processing a XeLaTeX source file the yellow lines the
cross-reference between pdf and source file and vice versa is
completely broken.
2. This happens after I updated to Ubuntu 11.10, TexLive
\
As far as PATH is concerned, I can run tlmgr update --all from my home
path, I think that means PATH works fine. Right?
But the real problem is in TeXWorks, the go to pdf and go to source
files functions are completely broken, that's the real issue.
Greetings
--
/Alessandro Ceschini
checked this.
To Ross:
So, are you suggesting I should downgrade to TL 2010? Previously I was
using just that version, without any apparent problem, all started when
I upgraded to TL 2011 (but after a fresh install, so no remnants of TL
2010 on my hard disk).
Regards
--
/Alessandro Ceschini
:
Of course I did update, I actually run sudo tlmgr update --all every day.
Greetings
--
/Alessandro Ceschini/
\documentclass[a4paper, 12pt, openany, draft]{book}
\usepackage{a4wide}
\usepackage{fontspec}
\usepackage{paralist}
\defaultfontfeatures{Mapping=tex-text}
\setmainfont{Tinos}
\usepackage
necessary, I'll ultimately subscribe to the mailing list. Just let me know.
Greetings
--
/Alessandro Ceschini/
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
is not
fontspec errors, it's the broken go-to functions in TeXWorks, none of
you use TeXWorks, right?
We also don't know if those fontspec errors are related with go-to
functions in TeXWorks, maybe it's just a coincidence that they happen to
occur together.
Greetings
--
/Alessandro Ceschini
'.
*
And, what's more, you do have a mess in both (2010 2011) pdf's instead
of the expected Greek letters, while I can see them correctly.
Again, the question is: is all this correlated to the breakdown of go-to
function in TeXWorks?
Greetings
--
/Alessandro Ceschini
To Peter:
Hi
Those warnings appear with practically every stuff that involves Unicode
or Opentype issues, from polytonic Greek to ligatures, to localized
glyphs, everything revolving around fontspec with whichever font, gives
me such warnings.
Greetings
--
/Alessandro Ceschini
Hi everybody
So, no one here has got problems with TeXWorks? Or am I the only user of
it around?
Greetings
--
/Alessandro Ceschini/
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
other LaTeX flavors in TeXWorks. What's for sure, that's that TeXWorks
is not the chief culprit here, the developers told me so:
http://code.google.com/p/texworks/issues/detail?id=550#makechanges Yet,
no one has apparently been able to reproduce my error.
Greetings
--
/Alessandro Ceschini
is that i gets capitalized in Turkish as
dotted I, that is: İ (U+0130) and this, XeLaTeX doesn't do. Is there a
way to enjoin it to do so?
**
--
Alessandro Ceschini
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman
, such type
of capitalization should be restricted to Turkish.
Thanks anyway, as far as my needs are concerned, this workaround
satisfies me.
--
/Alessandro Ceschini/
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman
:-\ ! This doesn't happen with PDF produced by LibreOffice
4.1, which now supports OpenType and therefore localised glyphs:
characters are correctly copied, and even if the recipient program
doesn't support OpenType, then standard glyphs are displayed.
--
/Alessandro Ceschini
Hello Ross,
I attached the whole output, not just the pdf, in the even that you wish
to check the .tex file as well. I've also attached the output, that is
the pasted text from the .pdf as it appears on LO. The font is always
the same, FreeSerif, bundled with Ubuntu.
Regards,
--
/Alessandro
Hello Ross,
I attached the whole output, not just the pdf, in the even that you wish
to check the .tex file as well. I've also attached the output, that is
the pasted text from the .pdf as it appears on LO. The font is always
the same, FreeSerif, bundled with Ubuntu.
Regards,
--
/Alessandro
Hello everybody,
This is indeed the latest version from SVN. However, even glyphs with
correct names' fail to be copied correctly, as you can see: so, maybe
this is not the real issue.
Regards,
--
/Alessandro Ceschini/
--
Subscriptions
,
--
/Alessandro Ceschini/
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
39 matches
Mail list logo
