You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(15) |
Nov
(37) |
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(13) |
Feb
(58) |
Mar
(61) |
Apr
(8) |
May
|
Jun
(18) |
Jul
(51) |
Aug
(11) |
Sep
(41) |
Oct
(19) |
Nov
(39) |
Dec
(14) |
2003 |
Jan
(46) |
Feb
(28) |
Mar
(3) |
Apr
(132) |
May
(93) |
Jun
(46) |
Jul
(22) |
Aug
(55) |
Sep
(13) |
Oct
(6) |
Nov
(8) |
Dec
(6) |
2004 |
Jan
(28) |
Feb
(60) |
Mar
(9) |
Apr
(28) |
May
(39) |
Jun
(40) |
Jul
(36) |
Aug
(13) |
Sep
(21) |
Oct
(38) |
Nov
(25) |
Dec
(8) |
2005 |
Jan
(6) |
Feb
(14) |
Mar
(1) |
Apr
(2) |
May
(17) |
Jun
(9) |
Jul
(7) |
Aug
(90) |
Sep
(44) |
Oct
(40) |
Nov
(22) |
Dec
(1) |
2006 |
Jan
(31) |
Feb
(10) |
Mar
(1) |
Apr
(3) |
May
(8) |
Jun
(28) |
Jul
(5) |
Aug
(42) |
Sep
(40) |
Oct
(40) |
Nov
(27) |
Dec
(26) |
2007 |
Jan
(14) |
Feb
(13) |
Mar
(3) |
Apr
(3) |
May
(22) |
Jun
|
Jul
|
Aug
(17) |
Sep
(10) |
Oct
|
Nov
(24) |
Dec
(5) |
2008 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(18) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(5) |
Oct
(3) |
Nov
(5) |
Dec
(3) |
2009 |
Jan
(17) |
Feb
(31) |
Mar
(5) |
Apr
(6) |
May
(15) |
Jun
(52) |
Jul
(48) |
Aug
(39) |
Sep
(6) |
Oct
(11) |
Nov
(8) |
Dec
(6) |
2010 |
Jan
(2) |
Feb
(3) |
Mar
(1) |
Apr
|
May
(3) |
Jun
(12) |
Jul
(1) |
Aug
|
Sep
(4) |
Oct
|
Nov
(4) |
Dec
(1) |
2011 |
Jan
(3) |
Feb
(21) |
Mar
(17) |
Apr
(8) |
May
(10) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(6) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(8) |
2013 |
Jan
(3) |
Feb
(7) |
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
(1) |
Feb
(12) |
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(9) |
Nov
(4) |
Dec
(1) |
2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(17) |
Jun
(4) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2016 |
Jan
(9) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(8) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
(10) |
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2019 |
Jan
|
Feb
(3) |
Mar
|
Apr
(17) |
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(1) |
2020 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
(11) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(4) |
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Dan K. <da...@ku...> - 2001-11-09 01:33:22
|
Below are the diffs for adding a '-strictlength <boolean>' flag to the ::textutil::adjust command as discussed in my previous email. Diffs for all modified files (textutil.n, adjust.tcl, and adjust.test) are included. I discovered what I believe to be a bug in the current implementation of the 'plain' justification when applied to $text2 from the .test file. I added test adjust-2.6 (which works now, but didn't work with CVS HEAD to test for the error condition. I am not used to not having CVS access, so this is my first patch/diffs that I am submitting. Let me know if you need anything else, or if I can do something to make this easier. I diffed against the CVS HEAD (actually against downloads of the CVS HEAD files). Let me know if you have any questions. Thanks, --Dan diff -w textutil2.n textutil.n 111a112,117 > .TP > \fI-strictlength boolean\fR > if set to \fIfalse\fR, a line can exceed the specified '-length' if > a single word is longer than '-length'. If set to \fItrue\fR, words > that are longer than '-length' are split so that no line exceeds > the specified '-length'. Default to \fIfalse\fR. ********************************************************************* diff -w adjust2.tcl adjust.tcl 8a9 > variable StrictLength 0 41a43 > variable StrictLength 0 74a77,82 > -strictlength { > if { ![ string is boolean -strict $value ] } then { > error "expected boolean but got \"$value\"" > } > set StrictLength [ string is true $value ] > } 76c84 < error "bad option \"$option\": must be -full, -justify or -length" --- > error "bad option \"$option\": must be -full, -justify, -length, or -strictlength" 85a94 > variable StrictLength 94a104,145 > > if { $StrictLength } then { > > # Limit the length of a line to $Length. If any single > # word is long than $Length, then split the word into multiple > # words. > > set i 0 > foreach tmpWord $ltext { > if { [ string length $tmpWord ] > $Length } then { > > # Since the word is longer than the line length, > # remove the word from the list of words. Then > # we will insert several words that are less than > # or equal to the line length in place of this word. > > set ltext [ lreplace $ltext $i $i ] > incr i -1 > set j 0 > > # Insert a series of shorter words in place of the > # one word that was too long. > > while { $j < [ string length $tmpWord ] } { > > # Calculate the end of the string range for this word. > > if { [ expr { [string length $tmpWord ] - $j } ] > $Length } then { > set end [ expr { $j + $Length - 1} ] > } else { > set end [ string length $tmpWord ] > } > > set ltext [ linsert $ltext [ expr {$i + 1} ] [ string range $tmpWord $j $end ] ] > incr i > incr j [ expr { $end - $j + 1 } ] > } > } > incr i > } > } > 226a278 > incr i 228c280 < set i -1 --- > set i 0 230d281 < incr i *********************************************************************** diff -w adjust2.test adjust.test 30a31,44 > set text2 "Hello, world! > This is the end, my friend. > > You're just another brick in the wall. > Michele, ma belle, sont des mots qui vont trs bien ensembles, > trs bien ensembles. > > ThisIsSimilarToTextOnlyThisStringHasOneReallyLongWordInIt > > Smoke on the water, and fire in the sky. > Oh Lord, don't let me be misunderstood. > > Cause tramp like us, baby we were born to run." > 166a181,231 > test adjust-2.6 {adjust multi lines with plain justification and long word} { > ::textutil::adjust $text2 -justify plain -length 31 -strictlength 1 > } \ > "Hello, world! This is the end, > my friend. You're just another > brick in the wall. Michele, ma > belle, sont des mots qui vont > tris bien ensembles, tris bien > ensembles. > ThisIsSimilarToTextOnlyThisStri > ngHasOneReallyLongWordInIt > Smoke on the water, and fire in > the sky. Oh Lord, don't let me > be misunderstood. Cause tramp > like us, baby we were born to > run." > > test adjust-2.7 {adjust multi lines with plain justification and strictlength} { > ::textutil::adjust $text2 -justify plain -length 31 -strictlength 1 > } \ > "Hello, world! This is the end, > my friend. You're just another > brick in the wall. Michele, ma > belle, sont des mots qui vont > tris bien ensembles, tris bien > ensembles. > ThisIsSimilarToTextOnlyThisStri > ngHasOneReallyLongWordInIt > Smoke on the water, and fire in > the sky. Oh Lord, don't let me > be misunderstood. Cause tramp > like us, baby we were born to > run." > > test adjust-2.8 {adjust multi lines with left justification and strictlength} { > ::textutil::adjust $text2 -justify left -length 31 -strictlength 1 > } \ > "Hello, world! This is the end, > my friend. You're just another > brick in the wall. Michele, ma > belle, sont des mots qui vont > tris bien ensembles, tris bien > ensembles. > ThisIsSimilarToTextOnlyThisStri > ngHasOneReallyLongWordInIt > Smoke on the water, and fire in > the sky. Oh Lord, don't let me > be misunderstood. Cause tramp > like us, baby we were born to > run." > 170a236 > unset text2 |
From: Andreas K. <and...@Ac...> - 2001-11-08 22:25:43
|
> -----Original Message----- > From: Dan Kuchler [mailto:da...@ku...] > Sent: Thursday, November 08, 2001 2:21 PM > To: je...@ac... > Cc: and...@ac... > Subject: Enhancement to ::textutil tcllib package > > > > Jeff and Andreas, > I have a possible enhancement for the ::textutil::adjust > procedure. > > I was using it today for a project, and it met all my > requirements except for one. I had a requirement that > the lines in the return string couldn't be longer than > the '-length' specified, even if the input line was longer > than '-length'. I accomplished this by splitting words > that were longer than '-length' into multiple words. > > Here is an example: > > package require textutil > > set foo "budget code 1: 01234567890-01234567890-01234567890 \ > budget code 2: 01234567890-01234567890-01234567890 some more text here." > > puts "foo: **[::textutil::adjust $foo -justify left -length 30]**" > > gives: > > foo: **budget code 1: > 01234567890-01234567890-0123456 > 7890 budget code 2: > 01234567890-01234567890-0123456 > 7890 some more text here.** > > With the original behaviour this would have > given: > > foo: **budget code 1: > 01234567890-01234567890-01234567890 > budget code 2: > 01234567890-01234567890-01234567890 > some more text here.** > > This patch/enhancement is useful when you have truly > fixed length fields (a database, entry widgets, etc.) > that you need to fit data into. The existing behavior > doesn't work because the line can be longer than the > '-length' specified if a single word is too long. > > I hardcoded this behavior but was wondering if it would > be worthwhile adding as an option. If you have any ideas > what I should call this option let me know. I would prefer this behaviour as an option. ... My shot at its name: -strict, or -strictlength (for strict length requirements) > If this is 'generally useful' I can submit a patch that > implements this as a flag instead of hard codes this. > > Thanks, > --Dan -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Jeff H. <Je...@Ac...> - 2001-11-07 21:05:47
|
WHAT: tklib v0.1 WHERE: http://tcllib.sourceforge.net/ WHY: By popular demand, I have created a sibling to tcllib for Tk library routines. I have only seeded it with a simple cursor module, but I hope that the many useful routines that others have created over time will find their way into this library. The development of tklib is in the same open manner as tcllib. Anyone is invited to join - all you need is a SourceForge id. Items that I know would be of interest: * image manipulation routines * canvas and text widget enhancement routines * megawidget libraries in all-tcl code * wizard builders * widget validation ... Also remember that the tcllib project has a 'tclapps' module for Tcl and/or Tk applications. This only has a couple apps now, but I plan on changing that in the near future, and others are encouraged to add to that module as well. -- Jeff Hobbs The Tcl Guy Senior Developer http://www.ActiveState.com/ Tcl Support and Productivity Solutions |
From: Reinhard M. <ma...@su...> - 2001-11-07 07:05:30
|
Hi, Jeff recently added me to the developer's list of tcllib. As a first action, I'll add the do-loop I created for the "Texas Tcl Shootout" to the control module. cu Reinhard |
From: Andreas K. <and...@Ac...> - 2001-11-07 00:29:59
|
> -----Original Message----- > From: tcl...@li... > [mailto:tcl...@li...]On Behalf Of Pat Thoyts > Sent: Tuesday, November 06, 2001 4:19 PM > To: tcl...@li... > Subject: [Tcllib-devel] New module for tcllib > > > -----BEGIN PGP SIGNED MESSAGE----- > > As part of working on supporting SMTP as a transport for TclSOAP I have > written a smtpd server that can go into tcllib. Following the structure > used with the ftp/ftpd packages I propose to create a new module 'smtpd' > and place the files in tcllib/modules/smtpd. > > The server implements the SMTP protocol and will accept mail from sendmail > and the tcllib smtp package. Once a mail transfer is completed the message > is passed to the user configured delivery procedure, so everything from > mail receipt on is up to the programmer using the package. > > So - any objections? No. Nevertheless, please place the new code with its supporting files (tests, docs) in a patch item on SF so that we others can have a look at the code before it is committed. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Jeff H. <Je...@Ac...> - 2001-11-07 00:28:14
|
> The server implements the SMTP protocol and will accept mail from sendmail > and the tcllib smtp package. Once a mail transfer is ... > So - any objections? Sounds good. |
From: Pat T. <Pat...@zs...> - 2001-11-07 00:20:03
|
-----BEGIN PGP SIGNED MESSAGE----- As part of working on supporting SMTP as a transport for TclSOAP I have written a smtpd server that can go into tcllib. Following the structure used with the ftp/ftpd packages I propose to create a new module 'smtpd' and place the files in tcllib/modules/smtpd. The server implements the SMTP protocol and will accept mail from sendmail and the tcllib smtp package. Once a mail transfer is completed the message is passed to the user configured delivery procedure, so everything from mail receipt on is up to the programmer using the package. So - any objections? Pat Thoyts mailto:pa...@zs... http://www.zsplat.freeserve.co.uk/resume.html PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBO+h97mB90JXwhOSJAQFm4QQAq7btM+m6ddKwJPnucXIGAC+8FbaV2gDg oTndaW+CslSjmvCFf+/xfacUg2VNbYKysZtIsRpsnl+Ypl4kV0ZH7wR1wPcsfHiJ bo3vX1pLiysULa88dZufdBJnHuM4kmJvf5lhHd61w3kbivBgfdaJJM3MB0qBtLQY GUfEIVy8EAs= =4FUG -----END PGP SIGNATURE----- |
From: Andreas K. <and...@Ac...> - 2001-11-06 19:03:26
|
> -----Original Message----- > From: tcl...@li... > [mailto:tcl...@li...]On Behalf Of Jeff Hobbs > Sent: Tuesday, November 06, 2001 11:00 AM > To: 'Brett Schwarz' > Cc: tcl...@li... > Subject: [Tcllib-devel] RE: tcllib 1.1 > > > > BTW, what version of Tcl do we write these modules for? Is it up to the > > module writer, or is there a convention? > > It is up to the module authors, but the 'package require Tcl 8.X' > should be clear at the top of the module. Most modules have [package require Tcl 8.2] and then make use of [string equal] and similar features. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Jeff H. <Je...@Ac...> - 2001-11-06 19:00:36
|
> BTW, what version of Tcl do we write these modules for? Is it up to the > module writer, or is there a convention? It is up to the module authors, but the 'package require Tcl 8.X' should be clear at the top of the module. Jeff |
From: Andreas K. <and...@Ac...> - 2001-11-06 18:53:53
|
> -----Original Message----- > From: tcl...@li... > [mailto:tcl...@li...]On Behalf Of Jeff Hobbs > Sent: Tuesday, November 06, 2001 10:38 AM > To: 'Brett Schwarz' > Cc: tcl...@li... > Subject: [Tcllib-devel] RE: tcllib 1.1 > > > I've added you to the tcllib users. You should subscribe as well > to tcllib-devel (see http://sourceforge.net/mail/?group_id=12883). > > We do have the project pages, but as I noted before, comp.lang.tcl > is still in such a noise-less state that discussing development > there is just as well for now. You can add the FRs to SF and then > close them when you commit. (assign to yourself) > > Also, note that other languages date/time/cal stuff is often > tied already into our 'clock' command, but there is definitely > room for adding more (just what tcllib is for). Welcome from me too. If you want to, have a look a the Pool packages too. See http://www.purl.org/net/akupries/soft/pool/ for documentation. There is quite a lot of stuff in there which should be migrated to tcllib (partially is). Pool_Clock should be of interest. > > Welcome! > > Jeff Hobbs The Tcl Guy > Senior Developer http://www.ActiveState.com/ > Tcl Support and Productivity Solutions > > > > -----Original Message----- > > From: Brett Schwarz [mailto:bre...@ya...] > > Sent: November 6, 2001 9:07 AM > > To: Jeffrey Hobbs > > Subject: Re: tcllib 1.1 > > > > > > What I wanted to do is a lib for date, time, calendar, etc. I > already have > > some procs to do this, I would just need to expand it (maybe looking at > > python, perl, java libs for other functionality). > > > > I looked at the feature list for tcllib, and I did not see > this, so I will > > post to c.l.t. as my intent to do this. Should I also add this as a > > feature request to tcllib? > > > > My SF account is: schwarzkopf > > > _______________________________________________ > Tcllib-devel mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcllib-devel -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Jeff H. <Je...@Ac...> - 2001-11-06 18:38:29
|
I've added you to the tcllib users. You should subscribe as well to tcllib-devel (see http://sourceforge.net/mail/?group_id=12883). We do have the project pages, but as I noted before, comp.lang.tcl is still in such a noise-less state that discussing development there is just as well for now. You can add the FRs to SF and then close them when you commit. (assign to yourself) Also, note that other languages date/time/cal stuff is often tied already into our 'clock' command, but there is definitely room for adding more (just what tcllib is for). Welcome! Jeff Hobbs The Tcl Guy Senior Developer http://www.ActiveState.com/ Tcl Support and Productivity Solutions > -----Original Message----- > From: Brett Schwarz [mailto:bre...@ya...] > Sent: November 6, 2001 9:07 AM > To: Jeffrey Hobbs > Subject: Re: tcllib 1.1 > > > What I wanted to do is a lib for date, time, calendar, etc. I already have > some procs to do this, I would just need to expand it (maybe looking at > python, perl, java libs for other functionality). > > I looked at the feature list for tcllib, and I did not see this, so I will > post to c.l.t. as my intent to do this. Should I also add this as a > feature request to tcllib? > > My SF account is: schwarzkopf |
From: Brent W. <we...@pa...> - 2001-11-06 18:26:16
|
Hello, list -- Brent Welch Software Architect, Panasas Inc Pioneering Smart and Infinitely Scalable Storage Networks www.panasas.com we...@pa... |
From: Donald G P. <dg...@em...> - 2001-11-02 16:33:12
|
Well, this morning's flood of old test messages confirms that I've got my sendmail masquerading problems resolved. Sorry about that flood; It did not occur to me that those queued messages would go on through after the problem was resolved. Also sorry to do the testing on a mailing list, but that was the only recipient address I had that reliably caused the problem. Now if I can just get a connection to news.teranews.com maybe I can have my communications back to normal... | Don Porter Mathematical and Computational Sciences Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| |
From: Don P. <dg...@em...> - 2001-11-02 16:18:54
|
ignore |
From: Don P. <dg...@em...> - 2001-11-02 16:18:50
|
this should fail |
From: Don P. <dg...@em...> - 2001-11-02 16:18:48
|
ignore |
From: Don P. <dg...@em...> - 2001-11-02 16:18:46
|
...from original machine DGP |
From: Don P. <dg...@em...> - 2001-11-02 16:18:42
|
blah blah |
From: Don P. <dg...@em...> - 2001-11-01 19:26:28
|
I think this should solve my e-mail problems... |
From: Andreas K. <and...@Ac...> - 2001-10-31 22:34:07
|
> -----Original Message----- > From: Oliver Bienert [mailto:obi...@gm...] > Sent: Wednesday, October 31, 2001 2:23 PM > To: tcllib-devel; Andreas Kupries > Subject: Re: [Tcllib-bugs] mime: -encoding 8bit > > > > >Hello all, > > > > >consider the following code: > > >(mv) 5 % mime::initialize -canonical text/html -encoding 8bit -param > > >{charset iso-8859-1} -file test.html > > >::mime::1 > > >(mv) 6 % mime::buildmessage ::mime::1 > > >Can't handle content encoding "8bit" > > > > >Am I missing something? The same appears, when I try to write > '-encoding > > >7bit'. Do I need some additional packages? > > > > What encodings are 7bit and 8bit ? Can you give me references to > > specifications > > defining them ? > > > > I know only of 'not encoded', 'base64', and 'quoted-printable'. > Hello Andreas, > > The following text I found in a pine-users mailing list: > > Here are details from the MIME > standard (http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html, MIME > Part One, > Section 6): > > The Content-Transfer-Encoding values "7bit", "8bit", and "binary" all > mean > that the identity (i.e. NO) encoding transformation has been > performed. Thanks for this information. Please log this as bug in the tcllib tracker at sourceforge, category mime or smtp, and assign it to me. I will take it from there. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Oliver B. <obi...@gm...> - 2001-10-31 22:21:44
|
> >Hello all, > > >consider the following code: > >(mv) 5 % mime::initialize -canonical text/html -encoding 8bit -param > >{charset iso-8859-1} -file test.html > >::mime::1 > >(mv) 6 % mime::buildmessage ::mime::1 > >Can't handle content encoding "8bit" > > >Am I missing something? The same appears, when I try to write '-encoding > >7bit'. Do I need some additional packages? > > What encodings are 7bit and 8bit ? Can you give me references to > specifications > defining them ? > > I know only of 'not encoded', 'base64', and 'quoted-printable'. > > -- > Andreas Kupries <and...@Ac...> > Developer @ http://www.ActiveState.com > Hello Andreas, The following text I found in a pine-users mailing list: Here are details from the MIME standard (http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html, MIME Part One, Section 6): The Content-Transfer-Encoding values "7bit", "8bit", and "binary" all mean that the identity (i.e. NO) encoding transformation has been performed. As such, they serve simply as indicators of the domain of the body data, and provide useful information about the sort of encoding that might be needed for transmission in a given transport system. The terms "7bit data", "8bit data", and "binary data" are all defined in Section 2. The quoted-printable and base64 encodings transform their input from an arbitrary domain into material in the "7bit" range, thus making it safe to carry over restricted transports. The specific definition of the transformations are given below. [...] Regards Oliver |
From: Don P. <dg...@go...> - 2001-10-31 19:50:15
|
...from another machine DGP |
From: Andreas K. <and...@Ac...> - 2001-10-31 19:27:46
|
Rerouted to tcllib development (tcllib-bugs is for the notifications from SourceForge when items in the tcllib trackers are changed) -----Original Message----- >From: tcl...@li... >[mailto:tcl...@li...]On Behalf Of Oliver >Bienert >Sent: Wednesday, October 31, 2001 11:20 AM >To: tcllib-bugs >Subject: [Tcllib-bugs] mime: -encoding 8bit >Hello all, >consider the following code: >(mv) 5 % mime::initialize -canonical text/html -encoding 8bit -param >{charset iso-8859-1} -file test.html >::mime::1 >(mv) 6 % mime::buildmessage ::mime::1 >Can't handle content encoding "8bit" >Am I missing something? The same appears, when I try to write '-encoding >7bit'. Do I need some additional packages? What encodings are 7bit and 8bit ? Can you give me references to specifications defining them ? I know only of 'not encoded', 'base64', and 'quoted-printable'. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Donald G P. <dg...@ca...> - 2001-10-31 03:57:52
|
ignore this one too |
From: Donald G P. <dg...@em...> - 2001-10-31 03:54:45
|
checking whether the list is accepting mail at all... | Don Porter Mathematical and Computational Sciences Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| |