| View previous topic :: View next topic |
| Author |
Message |
the doctor
Joined: 21 Apr 2009
Posts: 250
Location: DeLand, Florida USA
|
 Posted: Tue Oct 05, 2010 6:32 pm Post subject: RAR part numbering .r00 --> GROUPING |
 |
|
After parts in a RARs have used .r00 -.z99, RARs use the ASCII charaters - ASCII #123. The parts continue to be designated with ".{00 - .{99".
These other RAR part designations should be included to GROUP the headers.
And yes, I have, believe it or not, seen RARs that have so many parts that they have used parts designations beyond the .z99 point.
Of course these are not used very often but, should still be grouped properly and it should not be hard to add these additional characters to the make NewsLeecher group these RAR parts properly.
Last edited by the doctor on Thu Oct 07, 2010 6:08 pm; edited 3 times in total |
|
| Back to top |
|
 |
Smudge
Site Admin
Joined: 17 Aug 2004
Posts: 9832
|
| Posted: Wed Oct 06, 2010 2:27 am Post subject: |
|
|
NewsLeecher could probably be coded to support this (he recently added t-z support) but personally I think that the person creating the archive shouldn't allow it to get past z99. If there are that many parts in the archive, use the new naming scheme .part###.rar (which is why they changed to that scheme as default) or use larger archive segments. Instead of having the client support the bad creator, let's try to get the creator to do it 'right'
_________________
Please be aware of and use the following pages...
Services Status Page : SuperSearch and Usenet Access server status, retention, server load, indexing time, etc.
Support Request Form : Use this if you have a problem with billing or account status. The forum is only for NewsLeecher application issues.
_________________
It isn't God I have a problem with. It is his fan club I cannot stand. |
|
| Back to top |
|
|
sheepshagger
Joined: 16 Aug 2007
Posts: 457
|
| Posted: Wed Oct 06, 2010 8:37 am Post subject: |
|
|
| not sure it should be done just because of a few half assed posters who like to post differently to the conventional methods |
|
| Back to top |
|
|
the doctor
Joined: 21 Apr 2009
Posts: 250
Location: DeLand, Florida USA
|
| Posted: Wed Oct 06, 2010 1:33 pm Post subject: |
|
|
| Smudge wrote:
|
|
NewsLeecher could probably be coded to support this (he recently added t-z support) but personally I think that the person creating the archive shouldn't allow it to get past z99. If there are that many parts in the archive, use the new naming scheme .part###.rar (which is why they changed to that scheme as default) or use larger archive segments. Instead of having the client support the bad creator, let's try to get the creator to do it 'right'
|
Adding this support would be trivial.
Why not add support that properly and completely handles RAR compression specifications.
If you are going to have an RAR extract function in NewsLeecher then it should be based on the specifications of the compression method. Not on how someone should fomulate their post, but how RAR can be used to compress a file.
What you are saying is that it is ok for Newsleecher to do things half-way when it could easily do things the right way. |
|
| Back to top |
|
|
Smudge
Site Admin
Joined: 17 Aug 2004
Posts: 9832
|
| Posted: Wed Oct 06, 2010 7:45 pm Post subject: |
|
|
I don't believe that the rar spec would allow for old style naming to go beyond z99. I think it is a bug (oversight) that it is just incrementing the letter prefix and going too far. They probably didn't expect someone to create an archive over 1000 segments. I have sent an email to rarlab support asking about this situation.
I did a test on this a while back and yes you can create a rar archive with {## but it will fail to create |## as the pipe character is not allowed in a filename. I tested this on Windows, linux and OSX and they all stopped when attempting to create |00.
_________________
Please be aware of and use the following pages...
Services Status Page : SuperSearch and Usenet Access server status, retention, server load, indexing time, etc.
Support Request Form : Use this if you have a problem with billing or account status. The forum is only for NewsLeecher application issues.
_________________
It isn't God I have a problem with. It is his fan club I cannot stand. |
|
| Back to top |
|
|
the doctor
Joined: 21 Apr 2009
Posts: 250
Location: DeLand, Florida USA
|
| Posted: Thu Oct 07, 2010 1:12 am Post subject: |
|
|
| Smudge wrote:
|
I don't believe that the rar spec would allow for old style naming to go beyond z99. I think it is a bug (oversight) that it is just incrementing the letter prefix and going too far. They probably didn't expect someone to create an archive over 1000 segments. I have sent an email to rarlab support asking about this situation.
I did a test on this a while back and yes you can create a rar archive with {## but it will fail to create |## as the pipe character is not allowed in a filename. I tested this on Windows, linux and OSX and they all stopped when attempting to create |00.
|
You are correct about the "|" character not being used - now that you mention it, that character is excluded from the specification for exactly that reason - it is not able to be used in a file name - my error for including it.
I do not know why some people continue to use the old file naming scheme (.r00 - .{99) but, while they do NewsLeecher needs to properly support that naming scheme.
Last edited by the doctor on Thu Oct 07, 2010 1:31 pm; edited 1 time in total |
|
| Back to top |
|
|
sheepshagger
Joined: 16 Aug 2007
Posts: 457
|
| Posted: Thu Oct 07, 2010 9:01 am Post subject: |
|
|
| no it doesnt need to accomodate 0.01% of dick posters who insist on posting like that |
|
| Back to top |
|
|
the doctor
Joined: 21 Apr 2009
Posts: 250
Location: DeLand, Florida USA
|
| Posted: Thu Oct 07, 2010 12:32 pm Post subject: Definitive Confirmation - Roshal ARchive |
|
|
Roshal ARchive
Apparently my original source for info was wrong, the old RAR naming scheme stops at ".{99" according to Mr. Eugene Roshal the developer of the RAR compression and Winrar program.
Eugene sent the following reply in response to my email:
| Eugene Roshal wrote:
|
"Hello ...
It (RAR) will create ".{99"... No other characters are available.
It may be not the best approach, but it is here since the early nineties and we need to support it because of compatibility reasons.
...
Eugene"
|
(Quote edited to take out personal references and info)
So, only the ".{" character needs to be added (".r00" to ".z99" and include ".{00" to ".{99") to make NewsLeecher Grouping fully compatable with RAR compression.
45%-50% of the posts made in newsgroups use the ".r00" to ".{99" naming scheme. Since posts are larger and larger (full quality bluray movies etc.), more and more posts are going to occur using the maximum amount of rar parts and NewsLeecher does (as Mr. Roshal says) "...need to support it because of compatibility reasons." |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
