[25619] in Perl-Users-Digest
Perl-Users Digest, Issue: 7862 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Mar 6 14:06:01 2005
Date: Sun, 6 Mar 2005 11:05:28 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sun, 6 Mar 2005 Volume: 10 Number: 7862
Today's topics:
Re: another problem with look-around <nobull@mail.com>
Re: another problem with look-around eric.hall@gmail.com
beta testing <robin@infusedlight.net>
Re: cgi question kinda <nobull@mail.com>
Re: Cloning structures containing weak references (Ton Hospel)
Re: dividing strings <1usa@llenroc.ude.invalid>
Emacs modules for Perl programming (Jari Aalto+mail.perl)
Interpolation question worldcyclist@gmail.com
Re: Interpolation question <jl_post@hotmail.com>
Re: Interpolation question worldcyclist@gmail.com
Re: Interpolation question <jl_post@hotmail.com>
Re: Interpolation question <tadmc@augustmail.com>
Re: IO::Scalar insanity <please_post@nomail.edu>
Re: Looping through a log file <ebohlman@omsdev.com>
Re: Need to download exact copy of text file...little s <ebohlman@omsdev.com>
Re: PerlMagick, Annotate, and Webdings <flavell@ph.gla.ac.uk>
Re: PerlMagick, Annotate, and Webdings <aaron@daltons.ca>
Re: PerlMagick, Annotate, and Webdings <flavell@ph.gla.ac.uk>
Re: print isn't flashed using PERL by MSWin32 on Window <1usa@llenroc.ude.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 06 Mar 2005 09:07:22 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: another problem with look-around
Message-Id: <d0egu8$1km$1@sun3.bham.ac.uk>
eric.hall@gmail.com wrote:
> on Sat, 05 Mar 2005 21:09:04 +0000, Brian McCauley <nob...@mail.com>
> wrote:
>
>
>>/^(?!abc.*abc).*abc/
>
>
> That works in my specific case, so thanks. It doesn't work in the
> generalized case, since it requires the leading characters to match.
Opps, sorry, typo:
/^(?!.*abc.*abc).*abc/
------------------------------
Date: 6 Mar 2005 09:30:26 -0800
From: eric.hall@gmail.com
Subject: Re: another problem with look-around
Message-Id: <1110130226.518604.159690@l41g2000cwc.googlegroups.com>
On Sun, 06 Mar 2005 09:07:22 +0000, Brian McCauley <nob...@mail.com>
wrote:
> /^(?!.*abc.*abc).*abc/
excellent, thanks!
------------------------------
Date: 5 Mar 2005 21:42:41 -0800
From: "robin" <robin@infusedlight.net>
Subject: beta testing
Message-Id: <1110087761.522984.103340@f14g2000cwb.googlegroups.com>
if anyone is interested in beta testing this,
www.infusedlight.net/cgi-bin/bbs.pl - please report bugs with the link
at the bottom of the bulletin board. Later,
-Robin
------------------------------
Date: Sun, 06 Mar 2005 09:25:09 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: cgi question kinda
Message-Id: <d0ehvj$21o$1@sun3.bham.ac.uk>
Charlton Wilbur wrote:
>>>>>>"BW" == Brian Wakem <no@email.com> writes:
>
>
> BW> Shawn Corey wrote:
>
> >> Brian Wakem wrote:
> >>> $myvar =~ s!\n$!!;
> >>>
> >> chomp ($myvar);
> >>
> >> See perldoc -f chomp
>
> BW> TIMTOWTDI
>
> Yes, but they're not all good.
Yes, and in this situation chomp() is one that is not good.
> What does your code do when the string
> ends in \r\n on a platform where that's the line ending?
We're talking in this thread about text submitted via an HTML form. As
such the EOL convention on the platform where the client is running is
irrelevant. Text from HTML forms (on confirming browsers) is always
"\cM\cJ" delimited and AFAIK CGI.pm does not tranlate the EOL to the
local platform's EOL.
Note also that "\n" is not necessarily "\cJ" on all platforms.
I'm not quite sure what you need to do if the server is on a EBCDIC
platform.
------------------------------
Date: Sun, 6 Mar 2005 11:52:53 +0000 (UTC)
From: me-02@ton.iguana.be (Ton Hospel)
Subject: Re: Cloning structures containing weak references
Message-Id: <d0equl$5jl$1@post.home.lunix>
In article <422719fa$0$15582$4d3ebbfe@news1.pop-hannover.net>,
Tom Regner <regner@dievision.de> writes:
> Mintcake wrote:
>
>> I've tried various cloning modules to clone a structure containing weak
>> references.
>>
A recent enough storable will properly remember weakness of references.
------------------------------
Date: Sun, 06 Mar 2005 03:03:07 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: dividing strings
Message-Id: <Xns9610E0532FC23asu1cornelledu@127.0.0.1>
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote in
news:d0d657$ld7$1@mamenchi.zrz.TU-Berlin.DE:
> A. Sinan Unur <1usa@llenroc.ude.invalid> wrote in comp.lang.perl.misc:
>> while($cursor < length $source) {
>> my $chunk = substr($source, $cursor, $step);
>> unless($step == length $chunk) {
>> $target .= $chunk;
>> last;
>> }
>> $target .= $chunk . $insert;
>> $cursor += $step;
>> }
>>
>> print "Original: $source\nTransformed: $target\n";
>
> You're basically splitting the string into substrings of length at
> most $step and joining them back with $insert between them. Perl has
> high level functions that do this.
Yes, but I have a primitive mind
...
> On a different note, running through the insertion points backward,
> one can insert the fixed string directly:
>
> $target = $source;
> substr( $target, $_, 0) = $insert for reverse
> map $_*$step, 1 .. length( $target)/$step;
which I can improve by studying this.
Thanks.
Sinan.
------------------------------
Date: 06 Mar 2005 05:29:52 GMT
From: <jari.aalto <AT> poboxes.com> (Jari Aalto+mail.perl)
Subject: Emacs modules for Perl programming
Message-Id: <perl-faq/emacs-lisp-modules_1110086944@rtfm.mit.edu>
Archive-name: perl-faq/emacs-lisp-modules
Posting-Frequency: 2 times a month
URL: http://tiny-tools.sourceforge.net/
Maintainer: Jari Aalto A T poboxes com
Announcement: "What Emacs lisp modules can help with programming Perl"
Preface
Emacs is your friend if you have to do anything comcerning software
development: It offers plug-in modules, written in Emacs lisp
(elisp) language, that makes all your programmings wishes come
true. Please introduce yourself to Emacs and your programming era
will get a new light.
Where to find Emacs/XEmacs
o Unix:
http://www.gnu.org/software/emacs/emacs.html
http://www.xemacs.org/
o Unix Windows port (for Unix die-hards):
install http://www.cygwin.com/ which includes native Emacs 21.x.
and XEmacs port
o Pure Native Windows port
http://www.gnu.org/software/emacs/windows/ntemacs.html
ftp://ftp.xemacs.org/pub/xemacs/windows/setup.exe
o More Emacs resources at
http://tiny-tools.sourceforge.net/ => Emacs resource page
Emacs Perl Modules
Cperl -- Perl programming mode
http://www.cpan.org/modules/by-authors/id/ILYAZ/cperl-mode/
http://math.berkeley.edu/~ilya/software/emacs/
by Ilya Zakharevich
CPerl is major mode for editing perl files. Forget the default
`perl-mode' that comes with Emacs, this is much better. Comes
standard in newest Emacs.
TinyPerl -- Perl related utilities
http://tiny-tools.sourceforge.net/
If you ever wonder how to deal with Perl POD pages or how to find
documentation from all perl manpages, this package is for you.
Couple of keystrokes and all the documentaion is in your hands.
o Instant function help: See documentation of `shift', `pop'...
o Show Perl manual pages in *pod* buffer
o Grep through all Perl manpages (.pod)
o Follow POD references e.g. [perlre] to next pod with RETURN
o Coloured pod pages with `font-lock'
o Separate `tiperl-pod-view-mode' for jumping topics and pages
forward and backward in *pod* buffer.
o Update `$VERSION' variable with YYYY.MMDD on save.
o Load source code into Emacs, like Devel::DProf.pm
o Prepare script (version numbering) and Upload it to PAUSE
o Generate autoload STUBS (Devel::SelfStubber) for you
Perl Module (.pm)
TinyIgrep -- Perl Code browsing and easy grepping
[TinyIgrep is included in Tiny Tools Kit]
To grep from all installed Perl modules, define database to
TinyIgrep. There is example file emacs-rc-tinyigrep.el that shows
how to set up dattabases for Perl5, Perl4 whatever you have
installed
TinyIgrep calls Igrep.el to to do the search, You can adjust
recursive grep options, set search case sensitivity, add user grep
options etc.
You can find latest `igrep.el' module at
<http://groups.google.com/groups?group=gnu.emacs.sources> The
maintainer is Jefin Rodgers <kevinr <AT> ihs.com>.
TinyCompile -- To Browse grep results in Emacs *compile* buffer
TinyCompile is a minor mode for *compile* buffer from where
you can collapse unwanted lines or shorten file URLs:
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file1:NNN: MATCHED TEXT
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file2:NNN: MATCHED TEXT
-->
cd /asd/asd/asd/asd/ads/as/da/sd/as/as/asd/
file1:NNN: MATCHED TEXT
file1:NNN: MATCHED TEXT
End
------------------------------
Date: 5 Mar 2005 22:13:32 -0800
From: worldcyclist@gmail.com
Subject: Interpolation question
Message-Id: <1110089612.565556.48560@g14g2000cwa.googlegroups.com>
Any one have an idea why this first statement works just fine....
-------------------------------------------------------------------
($iso, $name, $size, $location) = $dbh->selectrow_array("SELECT `iso`,
`name`, `size`, `location` FROM `country_lookup` WHERE `name` =
\"France\"");
This works fine and this works fine also....
--------------------------------------------
$country_name = "France";
($iso, $name, $size, $location) = $dbh->selectrow_array("SELECT `iso`,
`name`, `size`, `location` FROM `country_lookup` WHERE `name` =
\"$country_name\"");
Where I am having a problem is if I try this....
--------------------------------------------------------
($country_name) = $dbh->selectrow_array('SELECT `category_label` FROM
`mt_category` WHERE `category_id` = '.$placement_category_id);
($iso, $name, $size, $location) = $dbh->selectrow_array("SELECT `iso`,
`name`, `size`, `location` FROM `country_lookup` WHERE `name` =
\"$country_name\"");
Invariably (no pun intended) I get this error....
Use of uninitialized value in concatenation (.) or string at......
I have used the variable $country_name in later places and it is fine.
Has anyone else experienced this?
Many thansk in advance...
Wilkie
------------------------------
Date: 6 Mar 2005 06:11:28 -0800
From: "jl_post@hotmail.com" <jl_post@hotmail.com>
Subject: Re: Interpolation question
Message-Id: <1110118288.374904.125100@f14g2000cwb.googlegroups.com>
worldcyclist@gmail.com wrote:
>
> Where I am having a problem is if I try this....
> --------------------------------------------------------
> ($country_name) = $dbh->selectrow_array('SELECT `category_label` FROM
> `mt_category` WHERE `category_id` = '.$placement_category_id);
>
> ($iso, $name, $size, $location) = $dbh->selectrow_array("SELECT
`iso`,
> `name`, `size`, `location` FROM `country_lookup` WHERE `name` =
> \"$country_name\"");
>
> Invariably (no pun intended) I get this error....
> Use of uninitialized value in concatenation (.) or string at......
>
> I have used the variable $country_name in later places and it is
fine.
Dear Wilkie,
Even though you used the variable $country_name in later places and
it is fine, apparently the Perl interpreter thinks it is undefined when
it gets to that line. Or maybe it's not complaining about
$country_name in the second line, but rather about
$placement_category_id in the first.
Whatever the reason, you can figure out what is wrong by placing the
following lines before that first call to selectrow_array():
print "\$placement_category_id is ";
print (defined $placement_category_id)
? "\"$placement_category_id\"\n"
: "UNDEFINED\n";
and the following lines before your second call to selectrow_array():
print "\$country_name is ";
print (defined $country_name)
? "\"$country_name\"\n"
: "UNDEFINED\n";
These lines will tell you exactly what the Perl interpreter thinks
the values for $placement_category_id and $country_name are as it tries
to evaluate those lines you are having trouble with.
This might also be a great time to learn how to use the Perl
debugger. If you can execute this script from a command line, then
start the debugger like this:
perl -d script.pl
At the debugger prompt, type "c line_num", where "line_num" is the line
number of that first selectrow_array() call. This will cause the
debugger to run UP TO that line (that line will NOT be executed).
Then type "x $placement_category_id" to see what the Perl interpreter
thinks is the value for $placement_category_id.
Then type "n" to execute that line of code and advance to right before
the next.
Then type "x $country_name" to see what the Perl interpreter thinks is
the value for $country_name.
Hopefully, at this point you've discovered what's wrong. If so, you
can type "q" to quit out of the Perl debugger.
I hope this helps you, Wilkie.
-- Jean-Luc
------------------------------
Date: 6 Mar 2005 08:20:44 -0800
From: worldcyclist@gmail.com
Subject: Re: Interpolation question
Message-Id: <1110126044.912366.151180@f14g2000cwb.googlegroups.com>
True to Occam's Razor the culprit has proven to be faulty data!
My country codes I had listed in the DB were preceeded a space!
It's always something simple it seems.
Jean - Luc, thank you SO very much for helping me with this.
By simply printing out the variable I caught the space.
Wilkie
jl_post@hotmail.com wrote:
> worldcyclist@gmail.com wrote:
> >
> > Where I am having a problem is if I try this....
> > --------------------------------------------------------
> > ($country_name) = $dbh->selectrow_array('SELECT `category_label`
FROM
> > `mt_category` WHERE `category_id` = '.$placement_category_id);
> >
> > ($iso, $name, $size, $location) = $dbh->selectrow_array("SELECT
> `iso`,
> > `name`, `size`, `location` FROM `country_lookup` WHERE `name` =
> > \"$country_name\"");
> >
> > Invariably (no pun intended) I get this error....
> > Use of uninitialized value in concatenation (.) or string at......
> >
> > I have used the variable $country_name in later places and it is
> fine.
>
>
> Dear Wilkie,
>
> Even though you used the variable $country_name in later places
and
> it is fine, apparently the Perl interpreter thinks it is undefined
when
> it gets to that line. Or maybe it's not complaining about
> $country_name in the second line, but rather about
> $placement_category_id in the first.
>
> Whatever the reason, you can figure out what is wrong by placing
the
> following lines before that first call to selectrow_array():
>
> print "\$placement_category_id is ";
> print (defined $placement_category_id)
> ? "\"$placement_category_id\"\n"
> : "UNDEFINED\n";
>
> and the following lines before your second call to selectrow_array():
>
> print "\$country_name is ";
> print (defined $country_name)
> ? "\"$country_name\"\n"
> : "UNDEFINED\n";
>
> These lines will tell you exactly what the Perl interpreter thinks
> the values for $placement_category_id and $country_name are as it
tries
> to evaluate those lines you are having trouble with.
>
> This might also be a great time to learn how to use the Perl
> debugger. If you can execute this script from a command line, then
> start the debugger like this:
>
> perl -d script.pl
>
> At the debugger prompt, type "c line_num", where "line_num" is the
line
> number of that first selectrow_array() call. This will cause the
> debugger to run UP TO that line (that line will NOT be executed).
>
> Then type "x $placement_category_id" to see what the Perl interpreter
> thinks is the value for $placement_category_id.
>
> Then type "n" to execute that line of code and advance to right
before
> the next.
>
> Then type "x $country_name" to see what the Perl interpreter thinks
is
> the value for $country_name.
>
> Hopefully, at this point you've discovered what's wrong. If so, you
> can type "q" to quit out of the Perl debugger.
>
> I hope this helps you, Wilkie.
>
> -- Jean-Luc
------------------------------
Date: 6 Mar 2005 09:00:52 -0800
From: "jl_post@hotmail.com" <jl_post@hotmail.com>
Subject: Re: Interpolation question
Message-Id: <1110128452.846274.72050@g14g2000cwa.googlegroups.com>
worldcyclist@gmail.com wrote:
>
> True to Occam's Razor the culprit has proven to be
> faulty data! My country codes I had listed in the
> DB were preceeded a space!
> It's always something simple it seems.
> Jean - Luc, thank you SO very much for helping me
> with this. By simply printing out the variable I
> caught the space.
I'm glad I could be of help. Often, successful debugging means
knowing where to place debug statements that will help you analyze
what's wrong.
Since you've already figured out what's wrong, this might sound
rather outdated, but I found a small (but significant) bug in the code
I sent you:
> > print "\$country_name is ";
> > print (defined $country_name)
> > ? "\"$country_name\"\n"
> > : "UNDEFINED\n";
The second print statement is immediately followed by an open
parenthesis. As a result of the motto "if it looks like a parameter
list, it is a parameter list," the print statement will try to print
the result of "defined $country_name" which is either a true value
(most likely "1") or a false value (most likely "").
Then, depending on the return value of print() (most likely "1"),
the string '\"$country_name\"\n" will be evaluated (but not printed),
not giving any output.
There are three ways to fix this problem:
1. Explicitly put in the "parameter parentheses", like this:
print((defined $country_name)
? "\"$country_name\"\n"
: "UNDEFINED\n");
2. Put a '+' (a plus sign) before the open parenthesis, which
lets the Perl interpreter know that the parentheses are not
"parameter parentheses":
print +(defined $country_name)
? "\"$country_name\"\n"
: "UNDEFINED\n";
3. Combine that statement with the previous print() statement,
so that there is no way for the parentheses to get mixed up
as "parameter parentheses":
print "\$country_name is ",
(defined $country_name)
? "\"$country_name\"\n"
: "UNDEFINED\n";
Sorry for going into detail about this when it's not really useful
to you anymore, but I thought it would be better if I fixed a mistake I
made that might have tripped you up and caused you confusion.
This is a common error for people new to Perl, but someone like me
should have known better. But, of course, we all make mistakes, so I
was just letting you know that if you encountered a problem using my
original print() statements, it was more likely my fault and not yours.
Sorry for the confusion, and I'm glad I could help.
-- Jean-Luc
------------------------------
Date: Sun, 6 Mar 2005 12:00:08 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Interpolation question
Message-Id: <slrnd2mh98.o47.tadmc@magna.augustmail.com>
jl_post@hotmail.com <jl_post@hotmail.com> wrote:
> Since you've already figured out what's wrong, this might sound
> rather outdated, but I found a small (but significant) bug in the code
> I sent you:
>
>> > print "\$country_name is ";
>> > print (defined $country_name)
>> > ? "\"$country_name\"\n"
>> > : "UNDEFINED\n";
>
> The second print statement is immediately followed by an open
> parenthesis.
> There are three ways to fix this problem:
Four, M'lord! [1]
> 1. Explicitly put in the "parameter parentheses", like this:
>
> print((defined $country_name)
> ? "\"$country_name\"\n"
> : "UNDEFINED\n");
>
> 2. Put a '+' (a plus sign) before the open parenthesis, which
> lets the Perl interpreter know that the parentheses are not
> "parameter parentheses":
>
> print +(defined $country_name)
> ? "\"$country_name\"\n"
> : "UNDEFINED\n";
Yuk! (IMHO)
> 3. Combine that statement with the previous print() statement,
> so that there is no way for the parentheses to get mixed up
> as "parameter parentheses":
>
> print "\$country_name is ",
> (defined $country_name)
> ? "\"$country_name\"\n"
> : "UNDEFINED\n";
4. Choose to use parenthesis on the _defined_ param list (best, IMO):
print "\$country_name is ";
print defined($country_name)
? "\"$country_name\"\n"
: "UNDEFINED\n";
But I would never inject all of those backslashes only to have to
filter them all back out when trying to understand the code:
print '$country_name is ';
print defined( $country_name )
? qq("$country_name"\n)
: qq(UNDEFINED\n);
[1] Wondering if DHA will notice that reference...
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sun, 6 Mar 2005 15:26:38 +0000 (UTC)
From: bill <please_post@nomail.edu>
Subject: Re: IO::Scalar insanity
Message-Id: <d0f7fe$k7m$1@reader1.panix.com>
In <d09qo0$92i$1@sun3.bham.ac.uk> Brian McCauley <nobull@mail.com> writes:
>bill wrote:
>> *STDIN = *SH;
>>
>> and many variants thereof, all of which fail silently.
>Should be:
> *STDIN = $SH;
>I tried testing it here but I've not got IO::Scalar installed (it's
>rendered obsolete by Perl5.8). I replaced
> my $SH = IO::Scalar->new(\$input);
>with
> open( my $SH, '<', \$input);
>Seemed to work OK.
This appears to be the way to go (assuming v5.8 is available). I
first tried (wishfully)
open(STDIN, '<', \$input)
which failed (for reasons I don't understand, but I imagine have
to do with the old fileno issue you mentioned), but this worked
open(my $SH, '<', \$input); # or die, etc.
*STDIN = $SH;
Thanks!
bill
------------------------------
Date: 5 Mar 2005 23:59:43 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: Looping through a log file
Message-Id: <Xns9610B86149FF8ebohlmanomsdevcom@130.133.1.4>
Tad McClellan <tadmc@augustmail.com> wrote in
news:slrnd2hrkg.7j6.tadmc@magna.augustmail.com:
> local $/ = "----------------------------------------\n";
What was that you said the other day about "fingerprints on the screen"?
:-)
------------------------------
Date: 6 Mar 2005 00:42:22 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: Need to download exact copy of text file...little squares replace carriage returns
Message-Id: <Xns9610BF9BFC426ebohlmanomsdevcom@130.133.1.4>
mortgages2005@aol.com wrote in news:1110050303.072893.58750
@g14g2000cwa.googlegroups.com:
> I need to download a text file from my server. I've tried to use a
> program to email it and another to make the browser download the file
> with a file save as dialog. The text file has a few charaters and then
> some spacing, as many as 120 spaces following by a new line. (line
> feed carriage return) I hear unix or linux stores a new line as a line
> feed only. After the file is saved to my hard disk through the save
> file routine, I should be able to open it up in notepad and not see a
> whole bunch of little squares which replaced all the carriage returns.
> I need an exact copy of the file as it is correctly saved on the
> server. I know it is correct because I'm able to drag it from my FTP
> client into my local browser and it opens up in notepad without the
> little squares. I can also even right click on the file on my server,
> and do view the file, which will transer it over to my computer, open
> it in notepad, and there won't be any square boxes replaceing the
> carriage returns.
As Gunnar pointed out, your requirements are contradictory. What you're
getting from your FTP server is *not* an "exact copy" of the file; rather
your FTP client and server are translating the line endings (by running
the connection in "ascii" rather than "binary" mode), exactly as your
script would if you used binmode().
Why do you need to maintain an "exact copy" locally in any case? If you
need to modify it locally and then FTP it to the server, the FTP process
will take care of translating the line endings back.
------------------------------
Date: Sun, 6 Mar 2005 00:08:14 +0000
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: PerlMagick, Annotate, and Webdings
Message-Id: <Pine.LNX.4.61.0503060002320.22988@ppepc56.ph.gla.ac.uk>
On Sat, 5 Mar 2005, Alan J. Flavell wrote:
> You're failing to specify the Unicode character for upward arrow.
> Possibly it's \x{2191} that you're looking for, but feel free to
> browse around the Unicode database.
Well, having now browsed the font, I see that it has your arrow in the
"private use area" at \x{f0e9} - since that's in the PUA, you won't
find the actual glyphs tabulated in the Unicode database.
That isn't a very robust way to use Unicode, but it *might* serve your
current purposes (untested in the specific context, sorry).
(still isn't a Perl problem, though, but I can't work out where best
to redirect it, so I'll stick. Apologies to the regulars.)
------------------------------
Date: Sun, 06 Mar 2005 07:38:43 -0700
From: Aaron Dalton <aaron@daltons.ca>
To: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: PerlMagick, Annotate, and Webdings
Message-Id: <422B15F3.1040407@daltons.ca>
Alan J. Flavell wrote:
> On Sat, 5 Mar 2005, Alan J. Flavell wrote:
>
>
>>You're failing to specify the Unicode character for upward arrow.
>>Possibly it's \x{2191} that you're looking for, but feel free to
>>browse around the Unicode database.
>
>
> Well, having now browsed the font, I see that it has your arrow in the
> "private use area" at \x{f0e9} - since that's in the PUA, you won't
> find the actual glyphs tabulated in the Unicode database.
>
I apologize. I obviously completely misunderstood my problem. I did
not understand all the issues surrounding Unicode. Really all I want is
for the PerlMagick module to use the glyph labeled Character+# in the
Webdings font table in my Annotate command. I've tried chr(#) to no
avail. I noticed a fair number of PerlMagick Q/A's in the newsgroup so
I ventured to ask the question. I will find a more germane venue to
explore. I do sincerely appreciate your time and response, however!
Cheers!
Aaron
------------------------------
Date: Sun, 6 Mar 2005 15:11:51 +0000
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: PerlMagick, Annotate, and Webdings
Message-Id: <Pine.LNX.4.61.0503061506550.31963@ppepc56.ph.gla.ac.uk>
On Sun, 6 Mar 2005, Aaron Dalton wrote:
> I apologize. I obviously completely misunderstood my problem.
Not at all. It's a very common structure clash (and - for all that I
knew - it *might* even have "worked" - I mean "worked" in the sense of
doing what the author intended, rather than in the sense which the
specifications require). But you say that it didn't, and that's where
I came in...
> Really all I want is for the PerlMagick module to use the glyph
> labeled Character+# in the Webdings font
Sure, I understand that; but that isn't how Unicode is meant to work,
and - since you said it wasn't doing what you intended, I drew the
conclusion that it was doing what Unicode intended instead.
I'm sorry I couldn't offer more concrete help in terms of this
particular software, though. Did anything useful happen when you
tried \x{f0e9} ? - from your lack of response, I presume the answer
must have been "no".
------------------------------
Date: Sun, 06 Mar 2005 00:39:16 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: print isn't flashed using PERL by MSWin32 on Windows XP
Message-Id: <Xns9610C7EFF9C40asu1cornelledu@127.0.0.1>
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote in
news:d0d391$jun$1@mamenchi.zrz.TU-Berlin.DE:
> A. Sinan Unur <1usa@llenroc.ude.invalid> wrote in comp.lang.perl.misc:
>> "reyal" <e_rozenblat@hotmail.com> wrote in
>> news:1110029222.643082.61680@f14g2000cwb.googlegroups.com:
>
> [eof() with a terminal]
...
> It appears to be consistent with the fact that eof() hangs until a
> character of input is available. It doesn't consume a character,
> but since on a terminal the eof condition is represented as a
> character it must look at one, so wait for one.
Ah, it's so obvious when you put it that way! Thanks :)
Sinan.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 7862
***************************************
