[NTG-context] Change in flushleft alignment?

2023-05-31 Thread Rik Kabel via ntg-context
Previously (May 7) flushleft paragraphs were as wide as possible within 
the text area. Now (May 30) they appear to be re-wrapped to a much 
narrower width.


Here is the same paragraph, showing the difference:

and

It looks like every paragraph has been run through par.

This does not seem to create paragraphs with more lines, but they create 
a very odd, choppy page. It does not prevent hyphenation, and sometimes 
introduces it where none was present before.


Did I miss a change?

--
Rik
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___


Re: [NTG-context] Mailing list problems

2023-05-31 Thread Pablo Rodriguez via ntg-context
On 5/31/23 16:21, Taco Hoekwater via ntg-context wrote:
> Hi!
>
> Both problems should be fixed now. If you still do not see the new
> posts in the ntg-context html archive page at
> https://mailman.ntg.nl/pipermail/ntg-context/2023/thread.html, force a
> hard reload of the page in your browser.

Hi Taco,

many thanks for your fix.

Best wishes,

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___


Re: [NTG-context] Mailing list problems

2023-05-31 Thread Taco Hoekwater via ntg-context
Hi!

Both problems should be fixed now. If you still do not see the new posts in the 
ntg-context html archive page at 
https://mailman.ntg.nl/pipermail/ntg-context/2023/thread.html , force a hard 
reload of the page in your browser.

Best wishes,
Taco

> On 28 May 2023, at 18:50, Mikael Sundqvist via ntg-context 
>  wrote:
> 
> Hi!
> 
> See https://tex.stackexchange.com/q/687020/52406. The OP there cannot 
> subscribe.
> 
> Looking at the web archive, it indeed seems to be missing several
> emails: https://www.mail-archive.com/ntg-context@ntg.nl/
> 
> I do not know who handles this, but... Ping!
> 
> /Mikael
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

— 
Taco Hoekwater  E: t...@bittext.nl
genderfluid (all pronouns)


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___


Re: [NTG-context] Super slow installation

2023-05-31 Thread Bruce Horrocks via ntg-context
On 31 May 2023, at 01:51, Thangalin  wrote:
> 
> From twelve99.net:
> 
> If you’re interested in our IP city prefixes, we have a lookup table on our 
> website: https://www.arelion.com/our-network/bgp-routing/bgp-communities 
> Scroll down to “Origin + Communities” and expand that section. You can see 
> that sea-b1 (your hop 8) is not in Brussels, but is our router in Seattle.
>  
> My guess would be that the hostname “us-was” for Liberty Global (aorta.net) 
> stands for U.S.A. and Washington D.C, not Warsaw. They’re probably using ICMP 
> tunneling for their MPLS backbone, that’s why the ping times are weird for 
> you.

Good point about the MPLS.

I was using https://www.geolocation.com/ to do the geolocation and it claims 
Warsaw but that - in hindsight - is wrong. So "us-was" is likely to be 
Washington as per the name and is also the device "taking the blame" for the 
entirety of the MPLS latency. Since that will include the transatlantic time 
the extra 75ms isn't quite so bad as it looks.

—
Bruce Horrocks
Hampshire, UK

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___