php-windows Digest 19 Aug 2013 06:36:09 -0000 Issue 4141
Topics (messages 31137 through 31140):
Simple method for generating PDF files for output/download, based on pretty
much just image content
31137 by: Jacob Kruger
Re: php can't resolve 8.3 paths to unicode filenames, is that expected ?
31138 by: R. S.
31139 by: Lester Caine
31140 by: Pierre Joye
Administrivia:
To subscribe to the digest, e-mail:
php-windows-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-windows-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-wind...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
Like subject line says, while have come across various modules/classes for
trying to handle all sorts of involved PDF output file generation, I pretty
much only need/want to spit out a PDF file containing something like a single
image file, or maybe one per page, and, yes, suppose, possibly with
PDF-specific forms of write-protection enabled - but that bits not necessarily
too important.
TIA
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
--- End Message ---
--- Begin Message ---
Pierre Joye wrote:
> Ok, now I can reproduce it. That's actually weird and have to look at it :)
Thank you!
> Ok, it looks like a found a bug, not in php but in the windows API.
> Which PHP version do you use (newest version uses a different CRT)?
I'm using 5.4.18
Lester Caine wrote:
> RS ... Just out of curiosity does the problem ranges of alphabets fall
> outside
> of the limited 'UTF16' range that M$ uses for 'wide strings'. I'm busy out at
> an
> exhibition this weekend so only have limited access to my database, but I do
> seem to recall that since wide strings are only 16 bit based, any character
> area
> going into the 24bit region (3 byte) is not supported.
I don't know. But it should be irrelevant since php interpreter doesn't see any
of the
non-ascii chars when given short path.
But anyway... Greek and Cyrylic letters are in the 3 byte range ? I thought
that only
applies to CKJ chars.
> This is
> definitively a bug in the CRT and I have to discuss that with my
> colleagues from the vc team.
Ok, so can you look at this bug report and tell me it is really a duplicate:
https://bugs.php.net/bug.php?id=65358
in the bugs marked as duplicate people tried to put non 7b chars actually
into php file handling functions while I do not.
Or there should be a new bug filled with precise statement that not all
shortened unicode paths are affected ?
--- End Message ---
--- Begin Message ---
R. S. wrote:
RS ... Just out of curiosity does the problem ranges of alphabets fall outside
>of the limited 'UTF16' range that M$ uses for 'wide strings'. I'm busy out at
an
>exhibition this weekend so only have limited access to my database, but I do
>seem to recall that since wide strings are only 16 bit based, any character
area
>going into the 24bit region (3 byte) is not supported.
I don't know. But it should be irrelevant since php interpreter doesn't see any
of the
non-ascii chars when given short path.
But anyway... Greek and Cyrylic letters are in the 3 byte range ? I thought
that only
applies to CKJ chars.
My memory is not as good as it once was, but I thought Greek was one of the
areas I had trouble with windows a few years back. I think at the time the
problem was that windows maps them to a different area using the 'spare' bit so
they are not the same characters as returned by unicode but applications have
nothing to indicate they are different.
Pierre I'm fairly sure that the 'wide string' codes get miss read and give
invalid unicode for what should be three byte blocks of codes. At the time I hit
it I was only using Borland C on Windows, but it sounds like the same problem I
hit when trying to port a system for a Greek customer. We ended up keeping
'english' file names but storing greek text :(
RS - It's not specifically a PHP bug as Pierre has indicated, you are just lucky
not to hit other manifestations of the problem.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--- End Message ---
--- Begin Message ---
hi,
On Sun, Aug 18, 2013 at 10:29 PM, R. S. <rs...@live.com> wrote:
> Pierre Joye wrote:
>
>> This is
>> definitively a bug in the CRT and I have to discuss that with my
>> colleagues from the vc team.
>
> Ok, so can you look at this bug report and tell me it is really a duplicate:
> https://bugs.php.net/bug.php?id=65358
> in the bugs marked as duplicate people tried to put non 7b chars actually
> into php file handling functions while I do not.
>
> Or there should be a new bug filled with precise statement that not all
> shortened unicode paths are affected ?
This bug report is enough, thanks for opening it!
Let follow up there and keep focus on the actual issue, which I
described earlier here and in this bug report.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--- End Message ---
