[mcclim-devel] #+unicode makes McCLIM not compile, #-unicode makes gadget-test-kr.lisp not compile.
As the title says, if I don't have :unicode in *features*, then Examples/gadget-test-kr.lisp won't compile. It calls make-text-style with 4 arguments in several places, when make-text-style only takes 3 arguments.
Having discovered that make-text-style /does/ take 4 arguments with #+unicode, I tried to recompile McCLIM after (push :unicode *features*). (:sb-unicode was already in *features*) This didn't work either:
compilation aborted because of fatal error: READ failure in COMPILE-FILE: READER-ERROR at 43712 (line 1046, column 88) on #<SB-SYS:FD-STREAM for "file "/home/dirk/lisp/mcclim/Backends/CLX/port.lisp"" {1000F83EA1}>: package "EXTERNAL-FORMAT" not found
Unicode support isn't important for me, but I was trying out the Examples/*.lisp and came across this, so I just thought I'd let you know.
Kind regards,
Dirk Gerrits
Dirk Gerrits writes:
As the title says, if I don't have :unicode in *features*, then Examples/gadget-test-kr.lisp won't compile. It calls make-text-style with 4 arguments in several places, when make-text-style only takes 3 arguments.
Having discovered that make-text-style /does/ take 4 arguments with #+unicode, I tried to recompile McCLIM after (push :unicode *features*). (:sb-unicode was already in *features*) This didn't work either:
compilation aborted because of fatal error: READ failure in COMPILE-FILE: READER-ERROR at 43712 (line 1046, column 88) on #<SB-SYS:FD-STREAM for "file "/home/dirk/lisp/mcclim/Backends/CLX/port.lisp"" {1000F83EA1}>: package "EXTERNAL-FORMAT" not found
Unicode support isn't important for me, but I was trying out the Examples/*.lisp and came across this, so I just thought I'd let you know.
The code in port.lisp that is withing #+unicode is just not working. There are missing functions that are required for it to work. That code and the example that uses it should probably be removed entirely. It was written as an experiment and needs a lot of work before it could be used directly.
Robert Strandh wrote:
The code in port.lisp that is withing #+unicode is just not working. There are missing functions that are required for it to work. That code and the example that uses it should probably be removed entirely. It was written as an experiment and needs a lot of work before it could be used directly.
OK, fair enough. Again, it isn't currently important for me, but it's just something I found while playing around...
Kind regards,
Dirk Gerrits
"RS" == Robert Strandh strandh@labri.fr writes:
RS> The code in port.lisp that is withing #+unicode is just not RS> working. There are missing functions that are required for it RS> to work. That code and the example that uses it should probably RS> be removed entirely.
May I suggest NOT removing the #+unicode code from port.lisp? It was a good guideline for me to make Unicode work in McCLIM. Perhaps I'm not the only one for whom Unicode support is very important.
Regards,
Milan Zamazal
Milan Zamazal writes:
May I suggest NOT removing the #+unicode code from port.lisp? It was a good guideline for me to make Unicode work in McCLIM. Perhaps I'm not the only one for whom Unicode support is very important.
The alternative, of course, is to make sure it works properly.
"RS" == Robert Strandh strandh@labri.fr writes:
RS> Milan Zamazal writes: >> >> May I suggest NOT removing the #+unicode code from port.lisp? It >> was a good guideline for me to make Unicode work in McCLIM.
[...]
RS> The alternative, of course, is to make sure it works properly.
Certainly. I think the presence of the experimental code may encourage someone to do it.
(I'm going to do something, but I don't need font sets, just a Unicode font, and I'm perhaps not going to go further than supporting the characters used in my language.)
Regards,
Milan Zamazal
-
Dirk Gerrits -
Milan Zamazal -
Robert Strandh