From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: randomizer line-breaking
Date: Tue, 8 Jun 2021 12:18:32 +0200 [thread overview]
Message-ID: <AC250771-CD02-4150-8ACA-08D0065C8079@st.estfiles.de> (raw)
In-Reply-To: <06430bc3-8a0b-fc16-5c4c-828a7f767ca2@xs4all.nl>
> Am 07.06.2021 um 17:59 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 6/7/2021 5:44 PM, Steffen Wolfrum wrote:
>>> Am 07.06.2021 um 16:39 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>>
>>> Not that I know of ... but you can run wiht --keeptuc and see if there are differences in the tuc file that create some oscillation.
>> Ok. Each run now creates 4 additional files:
>> file_name-tuc-02.tmp
>> file_name-tuc-03.tmp
>> file_name-tuc-04.tmp
>> file_name-tuc-05.tmp
>> Is this right?
> indeed and you can compare them to get some clue about what changes
>
> normally you get one so your style somehow triggers differences
Besides plenty of numbers that differ, there are also entire lines that differ:
One frequent difference for examples is line 2 (macros) and 3 (randomseed) in this:
utilitydata.job.variables.collected={
["macros"]={},
["randomseed"]=0x1.c14cd54cp-1,
["sectionblockorder"]={ "frontpart", "bodypart", "backpart" },
Another difference that pops up 1000 times is this line
["used"]="fit",
in situation like this:
utilitydata.structures.references.collected={
["02"]={
["*101"]={
["metadata"]=678,
["references"]={
["block"]="bodypart",
["internal"]=102,
["prefix"]="02",
["realpage"]=16,
["reference"]="*101",
["section"]=3,
["used"]="fit",
["view"]="fit",
["x"]=25526152,
["y"]=36448045,
},
},
Does this help?
PS: The entire problem began when I started using hyphenation-exceptions...
Steffen
___________________________________________________________________________________
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:[~2021-06-08 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 14:32 Steffen Wolfrum
2021-06-07 14:39 ` Hans Hagen
2021-06-07 15:44 ` Steffen Wolfrum
2021-06-07 15:59 ` Hans Hagen
2021-06-08 10:18 ` Steffen Wolfrum [this message]
2021-06-08 13:01 ` Hans Hagen
2021-06-08 13:15 ` Steffen Wolfrum
2021-06-08 13:30 ` Hans Hagen
2021-06-08 13:32 ` Steffen Wolfrum
2021-06-08 14:02 ` Hans Hagen
2021-06-08 14:16 ` Aditya Mahajan
2021-06-08 14:35 ` Steffen Wolfrum
2021-06-08 15:01 ` Hans Hagen
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=AC250771-CD02-4150-8ACA-08D0065C8079@st.estfiles.de \
--to=context@st.estfiles.de \
--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).