php-general Digest 21 Dec 2011 03:25:55 -0000 Issue 7619
Topics (messages 316073 through 316076):
Re: PDF Page Size
316073 by: Frank Arensmeier
316074 by: Floyd Resler
Re: PHP page source charset
316075 by: Jim Lucas
316076 by: Rick Dwyer
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
20 dec 2011 kl. 16.15 skrev Floyd Resler:
> What is a good solution for get the size of a PDF page in pixels? I've tried
> a few different methods but haven't had much success.
>
> Thanks!
> Floyd
If you don't mind using a command line tool, Xpdf would be my first choice.
Look out for "pdfinfo".
http://foolabs.com/xpdf/download.html
/frank
--- End Message ---
--- Begin Message ---
On Dec 20, 2011, at 10:49 AM, Frank Arensmeier wrote:
> 20 dec 2011 kl. 16.15 skrev Floyd Resler:
>
>> What is a good solution for get the size of a PDF page in pixels? I've
>> tried a few different methods but haven't had much success.
>>
>> Thanks!
>> Floyd
>
> If you don't mind using a command line tool, Xpdf would be my first choice.
> Look out for "pdfinfo".
>
> http://foolabs.com/xpdf/download.html
>
> /frank
>
That's perfect! Best solution I've seen!
Thanks!
Floyd
--- End Message ---
--- Begin Message ---
On 12/19/2011 6:44 PM, Rick Dwyer wrote:
> Hello all.
>
> When I set my page charset from iso-8859-1 to utf-8, when I run it through the
> W3C validator, the validator returns an error that it can't validate the page
> because of an illegal character not covered by UTF-8.
>
>
> "Sorry, I am unable to validate this document because on line 199 it contained
> one or more bytes that I cannot interpret as utf-8(in other words, the bytes
> found are not valid values in the specified Character Encoding). Please check
> both the content of the file and the character encoding indication.
> The error was: utf8 "\x99" does not map to Unicode"
>
> Line 199 is a line with my open PHP declaration:
> "<?php"
>
> Not sure why W3C is having a hard time with this. Any ideas?
>
> --Rick
>
>
You need to look at the output of your script, not the source for your script.
The validation only happens after PHP has executed & processed the php script
and sent the output to the browser. It is the source in the browser that the
validation script sees.
--
Jim Lucas
http://www.cmsws.com/
http://www.cmsws.com/examples/
http://www.bendsource.com/
--- End Message ---
--- Begin Message ---
On Dec 20, 2011, at 1:32 PM, Jim Lucas wrote:
On 12/19/2011 6:44 PM, Rick Dwyer wrote:
Hello all.
When I set my page charset from iso-8859-1 to utf-8, when I run it
through the
W3C validator, the validator returns an error that it can't
validate the page
because of an illegal character not covered by UTF-8.
"Sorry, I am unable to validate this document because on line 199
it contained
one or more bytes that I cannot interpret as utf-8(in other words,
the bytes
found are not valid values in the specified Character Encoding).
Please check
both the content of the file and the character encoding indication.
The error was: utf8 "\x99" does not map to Unicode"
Line 199 is a line with my open PHP declaration:
"<?php"
Not sure why W3C is having a hard time with this. Any ideas?
--Rick
You need to look at the output of your script, not the source for
your script.
The validation only happens after PHP has executed & processed the
php script
and sent the output to the browser. It is the source in the browser
that the
validation script sees.
--
Jim Lucas
Don't know what I was thinking when asked this as I am well aware PHP
is server side and already rendered at the point of the W3C validator.
--Rick
--- End Message ---
