View previous topic :: View next topic |
Should we use the draft-proposed subject lines now? |
I think, it's possible. |
|
27% |
[ 3 ] |
No way! Keep the "$F" at the end! |
|
72% |
[ 8 ] |
What's yEnc??? |
|
0% |
[ 0 ] |
|
Total Votes : 11 |
|
Author |
Message |
Tobias Rieper
Joined: 18 Feb 2002 Posts: 41 Location: Berlin, Germany
|
Posted: Thu Apr 18, 2002 5:53 am Post subject: yEnc subject lines |
|
|
Okay, I'm preparing my first yEnc post and have now to decide about the proper subject line.
Problem is, that the subject line format proposed in the yEnc draft will confuse some readers (esp. Agent) so that they can't autocombine the headers. That's why most posters aren't using the draft.
But nowadays the yEnc enabled readers (even Agent) can understand the draft-conform subject lines too.
So, is it possible to switch now or are there still too many old readers out there? (Or maybe some other incompatible readers.)
T.Rieper |
|
Back to top |
|
|
Onakra
Joined: 19 Feb 2002 Posts: 89 Location: Geldrop, Netherlands
|
Posted: Thu Apr 18, 2002 9:59 am Post subject: |
|
|
When I use the line "RequireFilenameWithTag=1" (default) in my agent.ini I still have problems with yEnc posts not combining when it's posted with Xnews. I haven't really paid attention to it, but do more recent versions of Xnews don't have that problem anymore? |
|
Back to top |
|
|
user
Joined: 19 Feb 2002 Posts: 72
|
Posted: Thu Apr 18, 2002 11:48 am Post subject: yatta yatta |
|
|
I just tried a few test posts using Xnews 5.03.24. Xnews still puts the filesize as the last thing on the subject line, but it seems to combine okay with Gravity (sorry, I don't have Agent installed.) But personally I'd prefer to have the filename at the very end as before. |
|
Back to top |
|
|
(inc)
Joined: 18 Feb 2002 Posts: 356 Location: San Diego
|
Posted: Thu Apr 18, 2002 2:47 pm Post subject: |
|
|
Browsing alt.binaries.test, if Agent has RequireFilenameWithTag=0, posts of both Xnews versions L5 & 5.03.24 will autojoin. If RequireFilenameWithTag=1, the L5 post will still autojoin, the 5.03.24 post will not. Going from L5 to 5.03.24, the yEnc was moved before the file name, and, more important to Agent, the segment count swapped places with the part size.
L5: file + yEnc + count + size
5.03.24: yEnc + file + size + count
(inc) |
|
Back to top |
|
|
Gorunova
Joined: 10 Feb 2002 Posts: 318 Location: Burnaby, B.C., Canada
|
Posted: Thu Apr 18, 2002 9:36 pm Post subject: |
|
|
I voted to keep the $F at the end, but I don't really feel strongly about it. It shouldn't matter much where the yEnc bit goes, because it's simple enough to grep for it. Identifying the filename and segment number is harder. Either way, software can and will be updated to handle the more popular format, or maybe even both, so it's only a temporary inconvenience. |
|
Back to top |
|
|
deoch
Joined: 09 Mar 2002 Posts: 65
|
Posted: Thu Apr 18, 2002 9:46 pm Post subject: |
|
|
It doesn't really matter to me, since I use Xnews... Either way.. |
|
Back to top |
|
|
HollyBerries
Joined: 06 Apr 2002 Posts: 32
|
Posted: Fri Apr 19, 2002 11:51 pm Post subject: |
|
|
I'm pretty sure that Agent 1.91 can handle traditional weird yENC subject lines now. Agent itself makes the subject line pretty darn funky when you tell it to encode in yENC, as evidenced by my recent Kanon ep 10 post in a.b.m.a.r. - it puts all kinds of weird stuff like how big the part is on the end after the file name. I still see spread out postings with Agent 1.91, but not when they're yENC, I don't think. Just when they've been posted with a space at the end or something.
Or quite possibly I'm smoking crack. One of the two |
|
Back to top |
|
|
|