From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Bug regarding placement and size of primes
Date: Thu, 15 Jun 2017 13:39:41 +0200 [thread overview]
Message-ID: <b22e2bb3-1736-a556-1c2b-55fd587be4c6@wxs.nl> (raw)
In-Reply-To: <AF6345E8-C9CF-4089-9592-DA88929B28F5@fa.uni-tuebingen.de>
On 6/15/2017 12:05 PM, Mathias Schickel wrote:
>> Am 12.06.2017 um 15:53 schrieb Mathias Schickel
>> <msch@fa.uni-tuebingen.de <mailto:msch@fa.uni-tuebingen.de>>:
>>
>> Thank you very much for providing the instructions, Mikael! Unfortunately
>>
>>> 1) get the files
>>>
>>> svn checkout --username anonsvn --password anonsvn
>>> https://serveur-svn.lri.fr/svn/modhel/luatex/branches/experimental/
>>
>> does not work on MacOS (which I am using). Can someone tell me which
>> command I need to use at MacOS (current version)?
>
> Can someone tell me how I can download the source of LuaTeX 1.0.5 and
> compile it on MacOS? Mikael wrote me instructions for Linux that did not
> work for MacOS. Thanks in advance!
>
> /Mathias
>
> PS: In the meantime I have read the thread
> https://mailman.ntg.nl/pipermail/ntg-context/2017/088747.html and seen
> that LuaTeX 1.0.5 is contained in the garden version on Windows. On my
> Windows machine everything regarding primes works really fine. Since
> LuaTeX 1.0.5 is not yet contained in the MacOS version I get the
> described bugs there. Does someone know when will LuaTeX 1.0.5 be
> officially released for MacOS?
>
>> 2) compile:
>>
>> step into the folder experimental and run build.sh
>>
>> 3) copy the luatex binary to a place where it is found
>>
>> I chose to replace the one from garden, and it seems to work.
>>
>> Good luck!
>>
>> /Mikael
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry
>> to the Wiki!
>>
>> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> /
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
>> archive : https://bitbucket.org/phg/context-mirror/commits/
>> wiki : http://contextgarden.net
>> ___________________________________________________________________________________
>
>
>> Am 12.06.2017 um 17:50 schrieb Mathias Schickel
>> <msch@fa.uni-tuebingen.de <mailto:msch@fa.uni-tuebingen.de>>:
>>
>>>
>>> Am 12.06.2017 um 17:10 schrieb Hans Hagen <pragma@wxs.nl
>>> <mailto:pragma@wxs.nl>>:
>>>
>>> On 6/12/2017 4:54 PM, Mathias Schickel wrote:
>>>>> the alternative is that i waste time again and again on getting
>>>>> something to work for all fonts and all combinations which leads to
>>>>> a mess that i then need to maintain without any gain
>>>> At first: Thank you very much for your work!
>>>>> so, i decided to follow a route that works for most fonts / cases
>>>>> and not some messy hybrid solution (and i don't want a different
>>>>> setup or bag of tricks for each font that is out there as that is a
>>>>> long term no-go)
>>>> But I have to contradict you here: It has nothing to do with special
>>>> or hybrid fonts. The problem persists at present (using the LuaTeX
>>>> version that is shipped with the Garden version) in /all/ fonts. The
>>>> primes are not rendered as they should in /any/ font I tried out.
>>>> As Mikael told me, you optimised the code for LuaTeX 1.05 which
>>>> seems to be terminated September this year. But until then the
>>>> output of primes will be not correct. I have no possibility to
>>>> switch back to the current (non-beta) version of ConTeXt, because
>>>> this version contains the bugs with primes you have already resolved.
>>>
>>> there will probably be a 1.0.5 one of these days (also for other
>>> reasons) but Mojca has to configure the garden compile farm
>>>
>>
>> Okay, that would be great. But could you tell me how I can get the
>> files and compile them? Mikael did write me instructions that work for
>> Linux, but I am on MacOS. My problem would be solved if I could get
>> the source and compile LuaTeX 1.05 on my own on MacOS. :-)
>>
>>>> This means that ConTeXt is not usable for me until LuaTeX 1.05 will
>>>> be released or until I am able to compile the source of LuaTeX 1.05
>>>> on my own. Some of the latest betas (the version one or two weeks
>>>> ago) did solve all problems regarding primes. The problem I am
>>>> referring to rose up in the most recent betas. As Mikael told me,
>>>> this is because you introduced new code to work with LuaTeX 1.05.
>>>> This is very nice, but because this version is not yet released,
>>>> this decision is questionable, since this makes ConTeXt unusable
>>>> until this release (if you need primes).
>>>> So I appreciate your hard work, but I would be nice to have a
>>>> version that runs with the current LuaTeX version of the beta of
>>>> ConTeXt (or alternatively it would be nice if instructions are
>>>> provided to compile the source of LuaTeX for every OS that can be
>>>> used simply).
>>>
>>> then just use old versions and then accept the bugs and limitations
>>> in those versions
>>
>> How can I get the beta of last week or the week before? In those betas
>> you have not yet included the new code (for use with LuaTeX 1.05) and
>> everything worked really fine. The --context=current garden version
>> has several bugs regarding primes you have solved in the mentioned
>> betas. So it would make no sense at all to use this version. I would
>> need one of the older betas or the most recent one with LuaTeX 1.05.
>>
>>>
>>>> And (to repeat myself) the problem has nothing to do with special
>>>> fonts of hybrid version or whatever. You get the problem using
>>>> standard Latin Modern or any font else. Simply try
>>> latin modern has all kind of issues ... and it's inconsistent with
>>> cambria, other gyre fonts etc ... in a decade of luatex and open type
>>> math fonts i captured a lot of font issues in runtiem fixes but that
>>> will always give side effects
>>>
>>> so, i can fix somethign for you with lm and then someone else
>>> complains about lucida etc etc
>>>
>>
>> I am not using Latin Modern. I only mentioned that because I wanted to
>> stress that I am not referring to exotic fonts. (I totally agree on
>> you regarding Latin Modern; I think Cambria should be the reference
>> since this font is the font that established the opentype math standard.)
>> In fact I am using Minion Math (which is a really stunning font) or
>> Stix 2. There had been no problems in those fonts with primes in the
>> betas of the last weeks. And as Mikeal suggests the problems are
>> resolved if I could use LuaTeX 1.05.
>>
>> So in fact the only thing I am complaining about is that everything
>> worked one or two betas ago until it is „broken“ in the newest beta
>> since this one seems to be based on code that requires LuaTeX 1.05
>> (which makes sense of course since this will be the upcoming release)
>> that is not shipped alongside the beta. So I am not able to understand
>> why code is provided in the beta that requires a LuaTeX version that
>> is not shipped alongside (and especially in view of the fact that we
>> had a perfectly working beta regarding primes last week; this means I
>> think it would have been a great idea to wait including the newest
>> code for primes that requires LuaTeX 1.05 until LuaTeX 1.05 is shipped
>> with the beta too). :-)
>>
>>> as i explained before, primes are a mess conceptually .. not a real
>>> character and not a proper superscript candidate either so when one
>>> corrects for one aspect one has to fight the other
>>>
>>> also, we have unicode and therefore multiple primes are one character
>>>
>>> i simply have no time (nor motivation) to spend days on some
>>> temporary solution that will be complained about also and discarded a
>>> while later anyway
>>
>> I perfectly understand that. And every work regarding primes is done,
>> as I think. But one way to make us of it would be to use the beta of
>> last week (or maybe the week before) or the most recent one together
>> with LuaTeX 1.05. But I have no idea how to make use of that ways. :-)
>>
>> So I am simply asking: How can I use older betas or how can I get the
>> source of LuaTeX 1.05 on a Mac and compile it?
Mojca is setting up the build bots so one of these days there will be
binaries.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-06-15 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:32 Mathias Schickel
2017-06-12 10:57 ` Mikael P. Sundqvist
2017-06-12 11:30 ` Mathias Schickel
2017-06-12 11:46 ` Mikael P. Sundqvist
2017-06-12 13:53 ` Mathias Schickel
2017-06-12 14:35 ` Hans Hagen
2017-06-12 14:54 ` Mathias Schickel
[not found] ` <04f76f77-ab92-1859-2fc3-62d25bfe69f3@wxs.nl>
2017-06-12 15:10 ` Fwd: " Hans Hagen
2017-06-12 15:50 ` Mathias Schickel
2017-06-15 10:05 ` Mathias Schickel
2017-06-15 11:39 ` Hans Hagen [this message]
2017-06-15 11:48 ` Mojca Miklavec
2017-06-15 12:01 ` Hans Hagen
2017-06-15 13:08 ` Mathias Schickel
2017-06-16 10:54 ` Mojca Miklavec
2017-06-16 14:59 ` Mathias Schickel
2017-06-16 5:49 ` luigi scarso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b22e2bb3-1736-a556-1c2b-55fd587be4c6@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).