long vocalic l isn't the sole problem. But even if it were, yes, it's a
big deal because linguists have to be able to say that ḹ doesn't occur. :-)
On Tue, 21 May 2019 at 09:34, BPJ wrote:
> Is it such a big deal? After all the long vocalic L occurs only in made up
> words.
>
>
Is it such a big deal? After all the long vocalic L occurs only in made up
words.
Den mån 20 maj 2019 20:44Steve White skrev:
> Dominic,
>
> I already wrote to somebody listed at the tiro.com website.
> Yes, please, you point out the issues to the Sanskrit2003 people.
>
> On Mon, May 20, 2019
Dominic,
I already wrote to somebody listed at the tiro.com website.
Yes, please, you point out the issues to the Sanskrit2003 people.
On Mon, May 20, 2019 at 7:40 PM Dominik Wujastyk wrote:
>
> Thank you for all this exploration, Steve!
>
> If you can talk to the Murty people, perhaps I can
Thank you for all this exploration, Steve!
If you can talk to the Murty people, perhaps I can try the Sanskrit 2003
folks. I've emailed with them successfully in the past, about (C) (which
is liberal but not well documented by them).
Dominik
I looked into the Sanskrit2003 font today.
The strange vertical mark seen in the samples of that font are easy to explain.
The glyph at U+0304 in the font is simply incorrect: it should be the
combining macron --- instead it is a double vertical line.
Other combining marks are missing in the
A few related points.
First, the issue with Murty Sanskrit and the l with dot below and
macron is of course a font issue.
Simply: the font is missing the glyph at U+1E39, which is exactly
LATIN SMALL LETTER L WITH DOT BELOW AND MACRON
I'll try to give the developers of that font a
In these tests, I'm using:
FreeSerif from the SVN *before* my attempt at a "fix" (r. 3391)
Sanskrit 2003 1.05 August 22, 2004
Murty Sanskrit 001.001
I found the particular way that the font is set in the source has a big effect.
I have no idea what is "right". But one produces better results.
Hi, all,
I have reproduced François' effect with FreeSerif, as well as
Dominik's effect with Sanskrit 2003.
I started with stock Linux Mint 19.1.
Then I installled TeXLive 2018 from the PPA of jonathonf/texlive-2018.
In the results of running xelatex on the sample, I did not see any
Hi Zdeněk,
I don't see anything amiss in my TL 2019 installation on Linux Mint.
(Only Murty Sanskrit shows some oddities)
However, even there XeLaTeX says:
Compiled with HarfBuzz version 1.7.6; using 1.7.6
I suspect the problem has something to do with Harfbuzz 2.3.1,
and I would very much like
Hi,
I can do it later this afternoon and I know how to build FreeFont from
your svn repo.
Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz
čt 16. 5. 2019 v 23:00 odesílatel Steve White napsal:
>
> Hi,
>
> I looked through the attachments to the previous
Hi,
I looked through the attachments to the previous postings, and some of the
images are consistent with the positioning feature being turned off.
That may now be fixed for FreeSerif.
However there were some that showed a completely wrong mark appearing,
far from the base mark. I have no idea
Hi Jonathan,
You may have a point, although I don't think it's the whole story.
(Most of what follows is font-techy. Upshot is: I did find suspicious
issues in FreeFont, and have now fixed them.)
The font feature in FreeSerif that positions generic marks like these is
mark ('generic marks
čt 16. 5. 2019 v 14:30 odesílatel Jonathan Kew napsal:
>
> On 16/05/2019 12:31, Ulrike Fischer wrote:
> > Am Mon, 13 May 2019 17:52:17 +0200 schrieb François Patte:
> >
> >> I have just made a fresh install of texlive 2019 and encountered a
> >> problem with the diacritical marks of romanized
On 16/05/2019 12:31, Ulrike Fischer wrote:
Am Mon, 13 May 2019 17:52:17 +0200 schrieb François Patte:
I have just made a fresh install of texlive 2019 and encountered a
problem with the diacritical marks of romanized sanskrit.
Do the 'dev2' script tables in FreeSerif include positioning
Am Mon, 13 May 2019 17:52:17 +0200 schrieb François Patte:
> I have just made a fresh install of texlive 2019 and encountered a
> problem with the diacritical marks of romanized sanskrit.
(copied from f.c.t.t):
One can see it with plain xetex too, and it is not the font (I'm
forcing it to
Saying
\setdefaultlanguage[Script=Latin]{sanskrit}
produces a correct result. So it's something to do with the
Script=Devanagari setting, I think.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 15/05/2019 à 02:06, Dominik Wujastyk a écrit :
>
> I don't think it's the font. I've just tried this MWE with several
> font choices,
>
> \documentclass{book} \usepackage{polyglossia}
> \setdefaultlanguage{sanskrit} \setmainfont{Sanskrit 2003}
st 15. 5. 2019 v 2:07 odesílatel Dominik Wujastyk
napsal:
>
> I don't think it's the font. I've just tried this MWE with several font
> choices,
>
> \documentclass{book}
> \usepackage{polyglossia}
> \setdefaultlanguage{sanskrit}
> \setmainfont{Sanskrit 2003}
> \begin{document}
> ā ī ū ṛ ṝ ḷ ḹ
I don't think it's the font. I've just tried this MWE with several font
choices,
\documentclass{book}
\usepackage{polyglossia}
\setdefaultlanguage{sanskrit}
\setmainfont{Sanskrit 2003}
\begin{document}
ā ī ū ṛ ṝ ḷ ḹ ṭ ḍ ṅ ś ṣ ḥ
\end{document}
Sanskrit 2003 gives this:
[image: image.png]
Murty
út 14. 5. 2019 v 23:21 odesílatel Steve White napsal:
>
> Hi Guys,
>
> I ran xelatex on your Tex file on my system, using a recent build of
> GNU FreeSerif.
> (I don't know if xetex is getting the font from the system
> installation or from its own installation.)
>
It depends on OS and on
Hi Guys,
I ran xelatex on your Tex file on my system, using a recent build of
GNU FreeSerif.
(I don't know if xetex is getting the font from the system
installation or from its own installation.)
As near as I can tell, the results are very good.
Did I miss something?
Is it possible that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 14/05/2019 à 13:32, Zdenek Wagner a écrit :
> Bonjour,
>
> I have not tried myself, I do not have TL 2019 yet but I would
> suspect it is a font related issue. It might (or might not) be
> related to these changes in svn:
>
>
Bonjour,
I have not tried myself, I do not have TL 2019 yet but I would suspect
it is a font related issue. It might (or might not) be related to
these changes in svn:
r3987 | Stevan_White | 2018-12-20 18:15:39 +0100 (Thu,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
I have just made a fresh install of texlive 2019 and encountered a
problem with the diacritical marks of romanized sanskrit.
See this mwe (compile it with and without \setdefaultlanguage{sanskrit}) :
24 matches
Mail list logo
