emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Daniel Clemente" <n142857@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: XHTML export - &nbsp; etc.
Date: Wed, 7 Nov 2007 19:04:07 +0100	[thread overview]
Message-ID: <ae9590aa0711071004j13f30df7nb6e81b00d0218de5@mail.gmail.com> (raw)
In-Reply-To: <87mytqkl9q.fsf@bzg.ath.cx>

>
> >    If you use C-x 8 SPC in a text file, you probably want to export it
> > as ~ in LaTeX, not to include that Unicode character directly.
>
> This is what i suggested.
>
   Ok, I misunderstood because you said „so we should avoid to handle
this in Org source file"

> > But this conversion is a strange one,
>
> Why?

   Well, I didn't know the character inserted by C-x 8 SPC, and I
suppose most people don't use it frequently. However, it could be used
and that would be simple. For instance:
 - you write C-x 8 SPC in your org files
 - C-x 8 SPC is exported to &nbsp; on HTML
 - C-x 8 SPC is exported to ~ on HTML
 - ~ continues working normally: produces ~ on HTML and \~{} on LaTeX


>
> > therefore it may be besser to offer a syntax for the ~ (non-breaking
> > space) in LaTeX. For instance \~ or ~
>
> I think I misunderstood at some point.  For me "\~" means "protect the
> tilde character from conversion" which means "don't escape the tilde",
> which results into a LaTeX nonbreaking-space (~).
>
   But we don't need to „protect the tilde from conversion" because ~
already writes the tilde unconverted.  \~ is still free to other uses.
   Sometimes the \ means „don't escape", sometimes not. For instance
at \- it wouldn't mean „insert a hyphen", but „breaking allowed".
   Yes, that's confusing...


Daniel

  reply	other threads:[~2007-11-07 18:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 12:13 XHTML export - customizing via local variables Adam Spiers
2007-11-02 12:20 ` XHTML export - &nbsp; etc Adam Spiers
2007-11-02 15:26   ` Bastien
2007-11-02 15:19     ` Adam Spiers
2007-11-02 15:33       ` Daniel Clemente
2007-11-02 15:34         ` Daniel Clemente
2007-11-02 19:21         ` Bastien
2007-11-02 18:50           ` William Henney
2007-11-02 20:20             ` Daniel Clemente
2007-11-03  0:06               ` Bastien
2007-11-04  0:00                 ` Daniel Clemente
2007-11-04 12:45                   ` Bastien
2007-11-07 16:09                     ` Daniel Clemente
2007-11-07 17:39                       ` Bastien
2007-11-07 18:04                         ` Daniel Clemente [this message]
2007-11-08  0:48                           ` Bastien
2007-11-09 19:51                             ` Daniel Clemente
2007-11-09 19:59                               ` Daniel Clemente
2007-11-09 22:37                                 ` Eddward DeVilla
2007-11-09 23:40                                   ` Xiao-Yong Jin
2007-11-12  5:07                                     ` Bastien
2007-11-12  5:22                               ` Bastien
2007-11-03  6:10               ` William Henney
2007-11-03 13:51                 ` Bastien
2007-11-03 14:23                   ` William Henney
2007-11-03 15:51                     ` Bastien
2007-11-03 16:46                       ` William Henney
2007-11-03  0:04             ` Bastien
2007-11-02 18:46       ` Bastien
2007-11-02 15:45 ` XHTML export - customizing via local variables Bastien

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.orgmode.org/

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

  git send-email \
    --in-reply-to=ae9590aa0711071004j13f30df7nb6e81b00d0218de5@mail.gmail.com \
    --to=n142857@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).