Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > free.control > #233 > unrolled thread

Re: cmsg newgroup free.snipe

Back to article view | Back to free.control

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: cmsg newgroup free.snipe "Adam H. Kerman" <ahk@chinet.com> - 2021-04-22 16:24 +0000
    Re: cmsg newgroup free.snipe snipeco.2@gmail.com (Sn!pe) - 2021-04-22 18:47 +0100
      Re: cmsg newgroup free.snipe "Adam H. Kerman" <ahk@chinet.com> - 2021-04-22 18:49 +0000
        Re: cmsg newgroup free.snipe snipeco.2@gmail.com (Sn!pe) - 2021-04-22 20:25 +0100
          Re: cmsg newgroup free.snipe "Adam H. Kerman" <ahk@chinet.com> - 2021-04-22 22:56 +0000
            Re: cmsg newgroup free.snipe snipeco.2@gmail.com (Sn!pe) - 2021-04-23 13:10 +0100

#233 — Re: cmsg newgroup free.snipe

Sn!pe <snipeco.1@gmail.com> wrote:
>For your newsgroups file:
>free.snipe      Release the wading bird.
           ^
Not a tab character; your composer isn't entering one

Can you enter it directly with the character code?

It's probably not going to prevent it from being appended to the
newsgroups file on most servers that create it.

>Charter:
>Dedicated to all who probe the boggy, marshy places of Usenet in search
>of things to eat.

>-- 
>^Ī^     <https://youtu.be/_kqytf31a8E>
  ^
You've got a UTF-8 character in your sigfile but your MIME header says
ISO-8859-1. I didn't notice that earlier.

>My pet rock Gordon just is.

[toc] | [next] | [standalone]

#234

Adam H. Kerman <ahk@chinet.com> wrote:

> Sn!pe <snipeco.1@gmail.com> wrote:
> >For your newsgroups file:
> >free.snipe      Release the wading bird.
>            ^
> Not a tab character; your composer isn't entering one
> 
> Can you enter it directly with the character code?
> 
> It's probably not going to prevent it from being appended to the
> newsgroups file on most servers that create it.
> 

Hmm, I don't understand that, I definitely used the tab key.  
Whatever, E-S has created it, as have aioe and Viper (which 
I think is a Highwinds reseller).  


> >Charter:
> >Dedicated to all who probe the boggy, marshy places of Usenet in search
> >of things to eat.
> 
> >-- 
> >^Ï^     <https://youtu.be/_kqytf31a8E>
>   ^
> You've got a UTF-8 character in your sigfile but your MIME header says
> ISO-8859-1. I didn't notice that earlier.
> 

MacSOUP does use UTF-8 when it has to, but falls back to lesser
encodings if it doesn't need the full UTF-8 charset.  I think "Latin
capital I with diaeresis" is an ISO-8859-1 character but I'm out of 
my comfort zone here.

<https://www.fileformat.info/info/charset/ISO-8859-1/list.htm>

-- 
^Ï^     <https://youtu.be/_kqytf31a8E>

My pet rock Gordon just is.

[toc] | [prev] | [next] | [standalone]

#235

Sn!pe <snipeco.1@gmail.com> wrote:
>Adam H. Kerman <ahk@chinet.com> wrote:
>>Sn!pe <snipeco.1@gmail.com> wrote:

>>>For your newsgroups file:
>>>free.snipe      Release the wading bird.
>>           ^
>>Not a tab character; your composer isn't entering one

>>Can you enter it directly with the character code?

>>It's probably not going to prevent it from being appended to the
>>newsgroups file on most servers that create it.

>Hmm, I don't understand that, I definitely used the tab key.  

This is a long-standing problem. Certain composers in newsreaders and
certain text editors are loathe to allow the use of a tab character, even
though it's ASCII, substituting a string of spaces. It's a feature but I
call it broken behavior. Well, that screws up the newsgroups file line
in a newgroup message. The problem is well known and News servers are
programmed to substitute the required tab upon processing the newgroup
message or creating the group.

>Whatever, E-S has created it, as have aioe and Viper (which 
>I think is a Highwinds reseller).  

Right, but the issue is whether the tab appears in the newsgroup file
itself.

You can see what INN does upon processing the newsgroups file line by
downloading the sample active and newsgroups files at

ftp://ftp.isc.org/pub/usenet/CONFIG

as those files aren't updated unless the newsgroups file line is in good
syntax but the tab substitution should be made.

>>You've got a UTF-8 character in your sigfile but your MIME header says
>>ISO-8859-1. I didn't notice that earlier.

>MacSOUP does use UTF-8 when it has to, but falls back to lesser
>encodings if it doesn't need the full UTF-8 charset.  I think "Latin
>capital I with diaeresis" is an ISO-8859-1 character but I'm out of 
>my comfort zone here.

You are correct that it's in the Latin 1 character set as Hex 00CF. I see the
UTF-8 multibyte character instead. It doesn't display correctly for me unless
I set the terminal emulation to display UTF-8.

><https://www.fileformat.info/info/charset/ISO-8859-1/list.htm>

[toc] | [prev] | [next] | [standalone]

#236

Adam H. Kerman <ahk@chinet.com> wrote:

> Sn!pe <snipeco.1@gmail.com> wrote:
> >Adam H. Kerman <ahk@chinet.com> wrote:
> >>Sn!pe <snipeco.1@gmail.com> wrote:
> 
> >>>For your newsgroups file:
> >>>free.snipe      Release the wading bird.
> >>           ^
> >>Not a tab character; your composer isn't entering one
> 
> >>Can you enter it directly with the character code?
> 
> >>It's probably not going to prevent it from being appended to the
> >>newsgroups file on most servers that create it.
> 
> >Hmm, I don't understand that, I definitely used the tab key.  
> 
> This is a long-standing problem. Certain composers in newsreaders and
> certain text editors are loathe to allow the use of a tab character, even
> though it's ASCII, substituting a string of spaces. It's a feature but I
> call it broken behavior. Well, that screws up the newsgroups file line
> in a newgroup message. The problem is well known and News servers are
> programmed to substitute the required tab upon processing the newgroup
> message or creating the group.
> 
> >Whatever, E-S has created it, as have aioe and Viper [edit].  
> 
> Right, but the issue is whether the tab appears in the newsgroup file
> itself.
> 
> You can see what INN does upon processing the newsgroups file line by
> downloading the sample active and newsgroups files at
> 
> ftp://ftp.isc.org/pub/usenet/CONFIG
> 
> as those files aren't updated unless the newsgroups file line is in good
> syntax but the tab substitution should be made.       [snip to end]
>

Interesting.  I see two free.* groups I've newgrouped in the past 
but not my two latest ones.  I assume that it takes time for 'active' 
and 'newsgroups' to be updated?  I'll keep an eye on this. 

-- 
^Ï^     <https://youtu.be/_kqytf31a8E>

My pet rock Gordon just is.

[toc] | [prev] | [next] | [standalone]

#237

Sn!pe <snipeco.1@gmail.com> wrote:
>Adam H. Kerman <ahk@chinet.com> wrote:
>
>> Sn!pe <snipeco.1@gmail.com> wrote:
>> >Adam H. Kerman <ahk@chinet.com> wrote:
>> >>Sn!pe <snipeco.1@gmail.com> wrote:
>> 
>> >>>For your newsgroups file:
>> >>>free.snipe      Release the wading bird.
>> >>           ^
>> >>Not a tab character; your composer isn't entering one
>> 
>> >>Can you enter it directly with the character code?
>> 
>> >>It's probably not going to prevent it from being appended to the
>> >>newsgroups file on most servers that create it.
>> 
>> >Hmm, I don't understand that, I definitely used the tab key.  
>> 
>> This is a long-standing problem. Certain composers in newsreaders and
>> certain text editors are loathe to allow the use of a tab character, even
>> though it's ASCII, substituting a string of spaces. It's a feature but I
>> call it broken behavior. Well, that screws up the newsgroups file line
>> in a newgroup message. The problem is well known and News servers are
>> programmed to substitute the required tab upon processing the newgroup
>> message or creating the group.
>> 
>> >Whatever, E-S has created it, as have aioe and Viper [edit].  
>> 
>> Right, but the issue is whether the tab appears in the newsgroup file
>> itself.
>> 
>> You can see what INN does upon processing the newsgroups file line by
>> downloading the sample active and newsgroups files at
>> 
>> ftp://ftp.isc.org/pub/usenet/CONFIG
>> 
>> as those files aren't updated unless the newsgroups file line is in good
>> syntax but the tab substitution should be made.       [snip to end]
>>
>
>Interesting.  I see two free.* groups I've newgrouped in the past 
>but not my two latest ones.  I assume that it takes time for 'active' 
>and 'newsgroups' to be updated?  I'll keep an eye on this. 

Russ doesn't run the update all that often anymore; maybe overnight.

[toc] | [prev] | [next] | [standalone]

#238

Adam H. Kerman <ahk@chinet.com> wrote:
[..]
> >> You can see what INN does upon processing the newsgroups file line
> >> by downloading the sample active and newsgroups files at
> >> 
> >> ftp://ftp.isc.org/pub/usenet/CONFIG
> >> 
> >> as those files aren't updated unless the newsgroups file line is in
> >> good syntax but the tab substitution should be made.    [snip to end]
> >>
> >
> >Interesting.  I see two free.* groups I've newgrouped in the past 
> >but not my two latest ones.  I assume that it takes time for 'active'
> >and 'newsgroups' to be updated?  I'll keep an eye on this. 
> >
>
> Russ doesn't run the update all that often anymore; maybe overnight.
>

I see both free.rocks and free.snipe are there now.  I do find 
this process fascinating, even if it is reducing Usenet to being 
my train-set.  Whatever, it's only free.* and I guess it does no 
harm to play with the machinery like this.

-- 
^Ï^     <https://youtu.be/_kqytf31a8E>

My pet rock Gordon just is.

[toc] | [prev] | [standalone]

Back to top | Article view | free.control

csiph-web