tl-install restore period

[Carlos]

On Wed, Apr 17, 2024 at 09:19:11PM +0900, Norbert Preining wrote:
> Hi
> 
> I'm an not sure what you are talking about, but it seems the mirror selected by the multiplexer is out of date or broken.
> 
> You can select any mirror manually using the
>   -repository ...
> argument.
> 
> Details here https://tug.org/texlive/doc/install-tl.html

Hey Norbert. Right. But when you follow the link as normal people would do through any terminal such as foot terminal or alacritty, it returns the infamous url not found . I'm not sure xterm would allow it but whenever you follow the link from a terminal 

the requested > > The requested URL is not found on this server. 

Better yet, you can try this out and go to 

https://tug.org/svn/texlive/trunk/Master/install-tl?revision=70922&view=markup

and see for yourself that when you click on the link from the online option

$0: The TeX Live versions of the local installation
and the repository being accessed are not compatible:
      local: $TeXLive::TLConfig::ReleaseYear
 repository: $texlive_release
Perhaps you need to use a different CTAN mirror?
(For more, see the output of install-tl --help, especially the
 -repository option.  Online via https://tug.org/texlive/doc.)

it's supposed to return a URL not found on the server and if it doesn't both your systems are duped to follow the link . 

After all both of you Karl and you are without exception and have been pretty lucky in this regards that all these modern browsers understand better the forward slash 

To include a dot is not common regardless of whatever the typographical gold standard happens to be 

See more about it in this question and answers here

https://webmasters.stackexchange.com/questions/73934/how-can-urls-have-a-dot-at-the-end-e-g-www-bla-de


and Look 

https://www.rfc-editor.org/rfc/rfc5322

Several productions in structured header field bodies are simply
   strings of certain basic characters.  Such productions are called
   atoms.

   Some of the structured header field bodies also allow the period
   character (".", ASCII value 46) within runs of atext.  An additional
   "dot-atom" token is defined for those purposes.

      Note: The "specials" token does not appear anywhere else in this
      specification.  It is simply the visible (i.e., non-control, non-
      white space) characters that do not appear in atext.  It is
      provided only because it is useful for implementers who use tools
      that lexically analyze messages.  Each of the characters in
      specials can be used to indicate a tokenization point in lexical
      analysis.


Resnick                     Standards Track                    [Page 12]

RFC 5322                Internet Message Format             October 2008


   atext           =   ALPHA / DIGIT /    ; Printable US-ASCII
                       "!" / "#" /        ;  characters not including
                       "$" / "%" /        ;  specials.  Used for atoms.
                       "&" / "'" /
                       "*" / "+" /
                       "-" / "/" /
                       "=" / "?" /
                       "^" / "_" /
                       "`" / "{" /
                       "|" / "}" /
                       "~"

   atom            =   [CFWS] 1*atext [CFWS]

   dot-atom-text   =   1*atext *("." 1*atext)

   dot-atom        =   [CFWS] dot-atom-text [CFWS]

   specials        =   "(" / ")" /        ; Special characters that do
                       "<" / ">" /        ;  not appear in atext
                       "[" / "]" /
                       ":" / ";" /
                       "@" / "\" /
                       "," / "." /
                       DQUOTE

   Both atom and dot-atom are interpreted as a single unit, comprising
   the string of characters that make it up.  Semantically, the optional
   comments and FWS surrounding the rest of the characters are not part
   of the atom; the atom is only the run of atext characters in an atom,
   or the atext and "." characters in a dot-atom.






> 
> 
> -- 
> PREINING Norbert                              https://www.preining.info
> arXiv / Cornell University  +   IFMGA ProGuide    +   TeX Live
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> 
> Apr 17, 2024 21:13:13 Carlos <linguafalsa at gmail.com>:
> 
> > Hello Karl:
> > 
> > I noticed the last message to the list didn't go through at tlbuild so here then
> > 
> > The changes for the trailing period had to be undone. And I'm fine with it. if that's what you want, so be it.
> > 
> > But my question is what browser am I supposed to use to follow the link in and thus avoid the infamous Not Found
> > The requested URL was not found on this server.
> > 
> > in all current browsers known to mankind
> > 
> > The TeX Live versions of the local installation
> > and the repository being accessed are not compatible:
> >       local: $TeXLive::TLConfig::ReleaseYear
> > repository: $texlive_release
> > Perhaps you need to use a different CTAN mirror?
> > (For more, see the output of install-tl --help, especially the
> > -repository option.  Online via https://tug.org/texlive/doc.)
> > 
> > Is it a text based browser like lynx or elinks or anything else that would allow me to read the page ?
> > 
> > What is it am I supposed to do when I follow the link from the terminal such as foot terminal or alacritty? Append a dot/period at the end so I can avoid the URL not found 
> > 
> > If the answer is a no to all these questions, could you add to the documentation something in the lines to advise the user to append a period/dot at the end of the URL? Or copy the link just before but not either on or after the dot/period in question?
> > 
> > But I mean.My gosh. Why does it to have so complicated?
> > 
> > 
> > 
> > 
> 
> 

--