source files encodings
Created by: avodonosov
The encoding used by lisp implementation to read source files is often depends on environment. Example, when GDL doesn't build because the default encoding used by lisp implementation is not UTF-8: http://cl-test-grid.appspot.com/blob?key=792731
If you want the sources to be more reliably build on systems were UTF8 is not default encoding, you may specify the encoding in your .asdf files:
#+asdf-unicode :encoding #+asdf-unicode :utf-8
The chapter about source file encoding in ASDF manual: http://common-lisp.net/project/asdf/asdf/Miscellaneous-additional-functionality.html#Miscellaneous-additional-functionality
P.S. you may find build status of genworks-gdl and other libraries on different lisps here: http://common-lisp.net/project/cl-test-grid/library/
Imported comments:
By genworks on 2012-11-30 16:14:55 UTC
Dear Anton,
Thank you very much for this report and for your great work.
The reports will give us a valuable head-start on getting our library to work with as many Lisps as possible. Currently we are supposed to work on ACL, LispWorks, and SBCL, so I will focus on getting those straightened out first of all. I will keep you apprised on progress.
By the way I am still trying to figure out how to move forward with CLF, and will let you know about any major progress on that front as well.
Regards
Dave
On Fri, Nov 30, 2012 at 9:58 AM, Anton Vodonosov notifications@github.comwrote:
The condising used by lisp implementation to read source files is often depends on environment. If you want the sources to be more reliably build on systems were UTF8 is not default encoding, you may specify the encoding in your .asdf files:
#+asdf-unicode :encoding #+asdf-unicode :utf-8
The chapter about source file encoding in ASDF manual:
P.S. you may find build status of genworks-gdl and other libraries on different lisps here: http://common-lisp.net/project/cl-test-grid/library/
— Reply to this email directly or view it on GitHubhttps://github.com/genworks/Genworks-GDL/issues/41.
--
My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699
By genworks on 2012-12-13 15:28:27 UTC
Hi Anton,
I don't think we really need our source files to be in UTF-8. It might be simpler if we can just convert all our files into a more basic encoding (normal ASCII, right?) I think some files got into UTF-8 because we have some examples with Chinese characters in there. But those examples are not necessary for basic Gendl to build and function.
What do you think?
By avodonosov on 2012-12-13 16:24:11 UTC
Restricting the source code to basic-latin will work too.
On the other hand most of the CL implementations (including the recent SBCL releases) support utf-8 and have suficiently recent ASDF so that the #+asdf-unicode conditionalized part of .asd will be in effect.
So, what of the two solutinos to chose is mostly what is more convenient to you: tranfrom the files to basic latin, or add the #+asd-unicode specification to the ASDF system which includes these examples.
By genworks on 2012-12-18 04:18:20 UTC
I believe the offending files are now converted to basic-latin (latin1 or iso-8859).
FYI, in order to Gendl (genworks-gdl) to be expected to build in CLs other than Allegro, LispWorks, and SBCL, we still have to add platform-specific directives to the several genworks.lisp files distributed throughout the codebase (there are eight of them, as follows:
./build/source/genworks.lisp ./gdl/apps/translators/xml/source/genworks.lisp ./gdl/apps/yadd/source/genworks.lisp ./gdl/base/common/genworks.lisp ./gdl/cl-lite/source/genworks.lisp ./gdl/geom-base/prereqs/source/genworks.lisp ./gdl/gwl/source/genworks.lisp ./regression/utils/source/genworks.lisp
it is not necessary for all of these to be updated for a basic build to work -- pretty much only
gdl/base/common/genworks.lisp gdl/cl-lite/source/genworks.lisp gdl/geom-base/prereqs/source/genworks.lisp gdl/gwl/source/genworks.lisp
will be enough for the core essentials to build and function.
Also, portableallegroserve.
).
By genworks on 2012-12-20 21:50:33 UTC
I'm closing this issue now. Please re-open it or let me know if any of the encodings continue to give problems. By the way note that we have recently ported to CCL, so we should build and run on all supported CCL platforms. You need the latest Sourceforge git of portableaserve and the latest github of Genworks-gdl for it to work (or just wait for the December 2012 Quicklisp release of everything).
By avodonosov on 2012-12-20 21:52:36 UTC
I know, I read CCL devel.
We will see the difference when next quicklisp is out and cl-test-gird will collect results from it.
By avodonosov on 2013-01-13 17:00:39 UTC
Most of the systems fixed, but one still fails: gdl-demos. http://cl-test-grid.appspot.com/blob?key=941904
By genworks on 2013-01-13 17:13:58 UTC
Hi Anton,
Thank you for checking back.
Yep, indeed that locales.lisp is still in UTF-8 and is full of Chinese characters. I will decide whether to go ahead and make the gdl-demos.asd system be in UTF-8, or weed that file out of the system and just manage it internally. If January Quicklisp release is this weekend, then I guess I'm too late already. Otherwise I will target next weekend.
Best Regards,
Dave
On Sun, Jan 13, 2013 at 12:00 PM, Anton Vodonosov notifications@github.comwrote:
Most of the systems fixed, but one still fails: gdl-demos. http://cl-test-grid.appspot.com/blob?key=941904
— Reply to this email directly or view it on GitHubhttps://github.com/genworks/Genworks-GDL/issues/41#issuecomment-12196322.
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699