develooper Front page | perl.perl5.porters | Postings from September 2000

Re: [ID 20000330.052] Use of uninitialized value in concatenation (.)

Thread Previous | Thread Next
From:
Nick Ing-Simmons
Date:
September 27, 2000 09:13
Subject:
Re: [ID 20000330.052] Use of uninitialized value in concatenation (.)
Message ID:
200009271611.RAA19036@mikado.tiuk.ti.com
Ilya Zakharevich <ilya@math.ohio-state.edu> writes:
>On Sat, Apr 01, 2000 at 09:44:49PM +0100, Nick Ing-Simmons wrote:
>> Ilya Zakharevich <ilya@math.ohio-state.edu> writes:
>> >On Sat, Apr 01, 2000 at 10:27:12AM +0100, Nick Ing-Simmons wrote:
>> >> The UNICODE support cannot really be finished till those of us with 
>> >> modules that can use it give it a try.
>> >
>> >What is the expected timeline for Tk831.000?
>> 
>> Difficult to say for sure. I am about to start the merge of Tcl/Tk sources,
>> until I see how messy that gets it is hard to guess at the scope of the 
>> problem. But I would like to have something by the conference.
>> Apart from the Tcl/Tk merge the main issue will be scheme to 
>> convert from UNICODE/UTF8 to the encodings of the various fonts a platform
>> may have. I am not yet convinced that the scheme Tcl uses for this is "right" 
>> but im-porting that is one option, another is making do with true
>> UNICODE encoded fonts for near term. 
>
>Did you have any progress with anything of this?  

I am just about at the point that tk8.3.2 based core passes Tk's
"make test":
Failed 3/25 test scripts, 88.00% okay. 18/904 subtests failed, 98.01% okay.

As yet there are no UTF8 or encoding features in use. I have stubs which 
just use iso-8859-1.

Perl's UTF8 should suffice for tk's UTF8 needs.  
But for encoding translations perl still has nothing (unless someone
has sneaked something in while I was not looking). 
"Luckily" I am acting Pumpking - while Jarko is on vacation.
So if Tk issues proceed at their
current pace I may "port" tclEncode.c and lib/encode/*.enc 
and put them in Jarko's placeholder ext/Encode

>You also said that
>you might look in the way fonts are accessed on OS/2 (the change
>800.12=> 800.14 broke it, since the old-named system-specific utility
>functions are not called anymore...)

Yeah it all changed round. There are still system specific routines
but they are deeper down. And it has all changed again in the UTF8 aware
version. 
There is a fairly clean API that "platform" proviodes to rest of Tk.
The internals are IMHO horrible in the UNIX version.
I have not looked at Win32 font support at all yet.



>
>Ilya
-- 
Nick Ing-Simmons <nik@tiuk.ti.com>
Via, but not speaking for: Texas Instruments Ltd.


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About