emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Markup (=, ~) in word?
Date: Fri, 30 Oct 2015 10:24:04 +0100	[thread overview]
Message-ID: <m21tccaevf.fsf@krugs.de> (raw)
In-Reply-To: <87io5p2yss.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 29 Oct 2015 21:40:51 +0100")

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

Rasmus <rasmus@gmx.us> writes:

> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Hi
>>
>> I guess this is not possible (and has been asked before, but I can't
>> find it t the moment...)- but how can I export the following markup?
>>
>> simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID=
>>
>>
>> Export will be mainly LaTeX, but maybe also html.
>
> You could separate with ZERO WIDTH SPACE.  AFAIR, this requires
> (xe/lua)latex, though.  In org-mode-git, you can set #+latex_command.  You
> can also remove the zero width spaces with a filter.

Looks interesting - thanks.

For the moment, I'll jut use spaces and in the final version, I'll
consider all these options.

Thanks  lot,

Rainer

>
> E.g.
>
>     (defcustom rasmus/org-latex-unicode-to-tex  '((" " "~")
>                                                 (" " "\\,")
>                                                 ("​" ""))
>       "list of re rep pairs which are replaced during latex export")
>
>     (defun rasmus/org-latex-unicode-to-tex (text backend info)
>       "Replace unicode strings with their TeX equivalents.
>
>   Currently:  ' ' (no break space) to '~'
>               ' ' (thin space) to '\,'
>               '​'  (zero width space) to ''."
>       (when (org-export-derived-backend-p backend 'latex)
>         (cl-loop for (re rep) in rasmus/org-latex-unicode-to-tex do
>                  (setq text (replace-regexp-in-string re rep text t t)))
>         text))
>
>     (add-to-list 'org-export-filter-final-output-functions
>                  'rasmus/org-latex-unicode-to-tex)

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

      reply	other threads:[~2015-10-30  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 11:06 Markup (=, ~) in word? Rainer M Krug
2015-10-29 11:11 ` Matt Price
2015-10-29 11:21   ` Rainer M Krug
2015-10-29 14:04     ` Göktuğ Kayaalp
2015-10-29 14:07       ` Rainer M Krug
2015-10-29 14:23         ` Göktuğ Kayaalp
2015-10-29 17:08     ` Charles C. Berry
2015-10-29 18:26       ` Rainer M Krug
2015-10-29 20:40 ` Rasmus
2015-10-30  9:24   ` Rainer M Krug [this message]

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=m21tccaevf.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).