On Fri, Oct 09, 2009 at 12:26:25PM +0200, Oliver Fromme wrote:
Gary Kline kl...@thought.org wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's a dash), and so forth. Why does
this fail to
Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's a dash), and so forth. Why does
On Fri, 9 Oct 2009, Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's a dash),
Gary Kline kl...@thought.org wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's a
Lars Eighner wrote:
On Fri, 9 Oct 2009, Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's a
On Fri, 9 Oct 2009, Oliver Fromme wrote:
Gary Kline kl...@thought.org wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
Warren Block wrote:
Oliver Fromme wrote:
Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
hex back into ', , -- [that's
On Fri, 9 Oct 2009, Oliver Fromme wrote:
Warren Block wrote:
Oliver Fromme wrote:
Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner or script to translate
Warren Block wrote:
Oliver Fromme wrote:
Warren Block wrote:
Oliver Fromme wrote:
Gary Kline wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl one-liner
On Fri, 9 Oct 2009, Warren Block wrote:
On Fri, 9 Oct 2009, Oliver Fromme wrote:
Gary Kline kl...@thought.org wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char to be
used. I'm looking for a perl
On Fri, 9 Oct 2009, Oliver Fromme wrote:
Warren Block wrote:
Certainly \x will not help in sed; sed doesn't have it.
Right, that's an annoying flaw in sed (it doesn't even
support the \0 syntax for octal values, which is more
standard than \x).
From my perspective, sed is a tiny, gooey
Oliver Fromme wrote:
This isn't about regular expressions at all. This is
about replacing fixed strings.
Fixed strings are regular expressions. Pretty unexciting ones,
but perfectly valid none the less.
This has been your daily pedantry minute.
Cheers,
Matthew
--
Dr
Lars Eighner wrote:
On Fri, 9 Oct 2009, Warren Block wrote:
That's twice now people have suggested sed instead of perl. Why? For
many uses, perl is a better sed than sed. The regex engine is far
more powerful and escapes are much simpler.
Because sed is stable and perl is getting all
Lars Eighner wrote:
On Fri, 9 Oct 2009, Warren Block wrote:
On Fri, 9 Oct 2009, Oliver Fromme wrote:
Gary Kline kl...@thought.org wrote:
Whenever I save a wordpeocessoe file [OOo, say] into a
text file, I get a slew of hex codes to indicate the char
to be
15 matches
Mail list logo
