Raul, thanks for clarifications. One last detail:
On 01-Jun-01, 15:39 (CDT), Raul Miller <[EMAIL PROTECTED]> wrote:
> For programs with no relevant text manipulation facilities (cron and
> crontab), it's sufficient that UTF-8 is not mutilated. [UTF-8 is
> designed, remember, to be represented in terms of 8 bit characters.]
The one possible gotcha (I think) is the command string. Suppose the
command is
* * * * * echo "some string with UTF-8 encoded characters"
(By which I mean a string containing characters outside the ASCII
range). At present cron parses the command simply by reading everything
up to the end of the line ('\n'), char by char (in the C type sense of
'char'). Is there a guarantee that byte value representing '\n' won't
show up in the sequence? Solving this particular problem wouldn't be too
hard in cron, I think, but again, there's a lot of programs that do this
kind of parsing.
Steve
--
Steve Greenland <[EMAIL PROTECTED]>
