Re: IXIN 1.2 available
On Mon 03 Dec 2012 16:09, Thien-Thi Nguyen writes: > BTW, ‘a2ixin foo.sxml’ works fine under Guile 2. > Getting the .sxml in the first place is the problem, there. IIRC the problem here was entities like ©right; not being defined? For that you can use: -- Function: define-parsed-entity! entity str Define a new parsed entity. ENTITY should be a symbol. Instances of &ENTITY; in XML text will be replaced with the string STR, which will then be parsed. from (sxml ssax). The SXML modules don't do DTD parsing right now, for better or for worse. I hear the kids are using relax-ng and such things anyway. Cheers, Andy -- http://wingolog.org/
Re: [ANN] guile-colorized released!
On Wed 05 Dec 2012 03:43, Nala Ginrut writes: > You may post a trace result like that: > ===cut= > ,tr (use-modules (ice-9 colorized)) > ===end= FWIW this probably doesn't do what you want -- the use-modules form is actually evaluated twice: once at compilation time and again when it the compiled expression is run. The first one probably has the interesting side effects, but it happens outside of the trace. I hear you've fixed it since then, but wanted to mention this point :) Cheers, Andy -- http://wingolog.org/
Re: displaying UTF8 characters in and out of a script (guile 2.0.5)
On Sun 16 Dec 2012 21:31, Mark H Weaver writes: > Also, since your script contains non-ASCII characters, you should place > a coding declaration in the file so that Guile will know what encoding > to use when reading it. If your script is in UTF-8, then put this in > the first 500 characters of the file: > > ;;; coding: utf-8 I think the default is utf-8 now, correct? Cheers, Andy -- http://wingolog.org/
Re: GNU Guile community in google+
Hi, I'm catching up with mail and thought you might be interested in my thoughts. They're just my thoughts, the thoughts of one Guile hacker, and I don't represent Guile with them -- so please do make up your own minds. I basically agree with Ludo and Mark that proprietary, centralized social networks are bad for society, and are dangerous because they are attractive. I agree with Zx that there are many ways that Guile could be better as a community -- especially among new and younger Guilers, many of whom have "come of age" in an internet sense on social networks. I think that Guile probably could engage with users who are already on proprietary social networks, in a kind of announcement-oriented way, but I agree that we as a project shouldn't try to build a community there. Perhaps we could have someone manage "official" accounts for Guile on these services and link them up to re-post things from our news feed. If there are community needs that are not being met right now, we should try to identify them and find solutions. Is a blog aggregator the thing, or is it something else? I liked the idea of a Guile subreddit, though I don't know if it could get enough interest. Is there something that we need to build into gnu.org somehow? Whatever we do, I think we should try to point people to the "primary" vehicles of discussion: the mailing lists and the IRC channel. Again, these are just opinions of one guy, take them as you will :) Cheers, Andy -- http://wingolog.org/
Re: displaying UTF8 characters in and out of a script (guile 2.0.5)
Andy Wingo writes: > On Sun 16 Dec 2012 21:31, Mark H Weaver writes: > >> Also, since your script contains non-ASCII characters, you should place >> a coding declaration in the file so that Guile will know what encoding >> to use when reading it. If your script is in UTF-8, then put this in >> the first 500 characters of the file: >> >> ;;; coding: utf-8 > > I think the default is utf-8 now, correct? Indeed, you are correct. I did not know that! Thanks, Mark
Re: displaying UTF8 characters in and out of a script (guile 2.0.5)
Andy Wingo skribis: > On Sun 16 Dec 2012 21:31, Mark H Weaver writes: > >> Also, since your script contains non-ASCII characters, you should place >> a coding declaration in the file so that Guile will know what encoding >> to use when reading it. If your script is in UTF-8, then put this in >> the first 500 characters of the file: >> >> ;;; coding: utf-8 > > I think the default is utf-8 now, correct? Yes. I just noticed that it’s only stealthily mentioned under “Compilation”: Each FILE is assumed to be UTF-8-encoded, unless it contains a coding declaration as recognized by `file-encoding' (*note Character Encoding of Source Files::). Ludo’.
