unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: Guile Mailing List <guile-user@gnu.org>
Subject: Re: escaping characters
Date: Thu, 1 Nov 2012 14:41:00 -0400	[thread overview]
Message-ID: <CA+U71=Oy3OhAJgkR=iXef5MCg6xWekM1Wnj0=eKECaKBuZgzpw@mail.gmail.com> (raw)
In-Reply-To: <87zk31ur6c.fsf@zigzag.favinet>

[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]

This is related to what ttn said, but I am a bit confused by the request.
Normally when you read *in* something like LaTeX source, you convert \\ to
\, and similar things. Then when you write *out* LaTeX source, you might
convert \ to \\. This is useful if, for instance, you want Guile to
automatically generate some LaTeX and then write it in a form that TeX will
read. Kejia seems to be asking for the opposite.

I certainly agree that it would be useful to have a general function for
this (and the reverse).

Noah


On Thu, Nov 1, 2012 at 2:14 PM, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:

>
> () Kejia柯嘉 <w.kejia@gmail.com>
> () Thu, 1 Nov 2012 10:24:52 -0400
>
>    for an example, when a program reads in a latex source, is there an
>    escape function that can rewrite all `\' to `\\', `"' to `\"', and so
>    on?
>
> This kind of escaping for backslash and double-quote (and other chars,
> depending on Guile flavor) is built-in for ‘(object->string STRING)’,
> but anything else (the "and so on" bit) you have to define for yourself,
> or find something already defined.
>
> For example, Guile-BAUX provides module ‘(guile-baux write-string)’
> which exports proc ‘write-string’ that handles twelve additional
> characters:
>
>
> http://www.gnuvola.org/software/guile-baux/guile-baux.html.gz#write_002dstring
>
> Another example is Guile-PG module ‘(database postgres-qcons)’, which
> has all manner of procs to DTRT for various "and so on" cases:
>
> http://www.nongnu.org/guile-pg/doc/qcons-quoting.html#qcons-quoting
>
> I think it would be nice for these procs (and perhaps your LaTeX
> oriented one, once defined) to be rebased onto a general one, hosted
> apart from any particular Guile version (perhaps Guile-Lib -- is that
> project still viable?).
>
> Or maybe i'm missing something already out there by now.  I remember
> fruitlessly searching a number of years back, but things may have
> changed since then.  Here's some related discussion:
>
> http://lists.gnu.org/archive/html/guile-user/2012-01/msg00114.html
>
> [cc trimmed]
>
> --
> Thien-Thi Nguyen ..................................... GPG key: 4C807502
> .                  NB: ttn at glug dot org is not me                   .
> .                 (and has not been since 2007 or so)                  .
> .                        ACCEPT NO SUBSTITUTES                         .
> ........... please send technical questions to mailing lists ...........
>
>

[-- Attachment #2: Type: text/html, Size: 3479 bytes --]

  reply	other threads:[~2012-11-01 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:47 escaping characters Kejia柯嘉
2012-10-31 21:34 ` Ludovic Courtès
2012-11-01 14:24   ` Kejia柯嘉
2012-11-01 18:14     ` Thien-Thi Nguyen
2012-11-01 18:41       ` Noah Lavine [this message]
2012-11-02 21:57     ` Ludovic Courtès
2012-11-01  2:12 ` nalaginrut
2012-11-02 17:05 ` Ian Price
2012-11-02 22:06   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+U71=Oy3OhAJgkR=iXef5MCg6xWekM1Wnj0=eKECaKBuZgzpw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=ttn@gnuvola.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).