bold font in org-e-beamer export

bold font in org-e-beamer export

[Suvayu Ali]

Hi Nicolas and others,

org-e-beamer exports *bold markup* as \alert{..}. I was wondering if
there is a way to export it as the usual \textbf{..}. I would also like
to have a convenient markup for \structure{..}, how do I add new markup?
It would be okay if I could alter existing markup to be exported as
\structure{..}; then I could use one of the less used ones. I saw there
is a defcustom, org-e-latex-text-markup-alist, for org-e-latex; but I
couldn't find a similar variable for org-e-beamer.

Thanks for any inputs.

-- 
Suvayu

Open source is the future. It sets us free.

Re: bold font in org-e-beamer export

[Nicolas Goaziou]

Hello,

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> org-e-beamer exports *bold markup* as \alert{..}. I was wondering if
> there is a way to export it as the usual \textbf{..}. I would also like
> to have a convenient markup for \structure{..}, how do I add new
> markup?

You can't add new markup.  

Though, there are already 4 symbols used for regular text and 2 for
verbatim text.  And you have full control over their output with
filters.

So, let's say "*" will produce \textbf{...} and "+" will produce
\structure{...}.

#+BEGIN_SRC emacs-lisp
(defun suvayu-beamer-bold (contents backend info)
  (if (not (eq backend 'e-beamer)) contents
    (replace-regexp-in-string "\\`\\\\[A-Za-z0-9]+" "\\\\textbf" contents)))

(defun suvayu-beamer-structure (contents backend info)
  (if (not (eq backend 'e-beamer)) contents
    (replace-regexp-in-string "\\`\\\\[A-Za-z0-9]+" "\\\\structure" contents)))

(add-to-list 'org-export-filter-bold-functions 'suvayu-beamer-bold)
(add-to-list 'org-export-filter-strike-through-functions
             'suvayu-beamer-structure)
#+END_SRC

You can also derive a new back-end from e-beamer that will behave
differently for bold and strike-through object types.


Regards,

-- 
Nicolas Goaziou

Re: bold font in org-e-beamer export

[Suvayu Ali]

Hi Nicolas,

On Wed, Jul 25, 2012 at 10:57:34AM +0200, Nicolas Goaziou wrote:
> Hello,
> 
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > org-e-beamer exports *bold markup* as \alert{..}. I was wondering if
> > there is a way to export it as the usual \textbf{..}. I would also like
> > to have a convenient markup for \structure{..}, how do I add new
> > markup?
> 
> You can't add new markup.  
> 
> Though, there are already 4 symbols used for regular text and 2 for
> verbatim text.  And you have full control over their output with
> filters.
> 

Your example below works wonderfully. However I have a question, for the
sake of understanding.

> So, let's say "*" will produce \textbf{...} and "+" will produce
> \structure{...}.
> 
> #+BEGIN_SRC emacs-lisp
> (defun suvayu-beamer-bold (contents backend info)
>   (if (not (eq backend 'e-beamer)) contents
>     (replace-regexp-in-string "\\`\\\\[A-Za-z0-9]+" "\\\\textbf" contents)))
> 
> (defun suvayu-beamer-structure (contents backend info)
>   (if (not (eq backend 'e-beamer)) contents
>     (replace-regexp-in-string "\\`\\\\[A-Za-z0-9]+" "\\\\structure" contents)))

I do not understand the above regular expressions. I guess \\` to match
the start of string (one extra backslash is required to escape the 2nd).
But I don't understand the four backslash sequence; I guess it inserts
\\ to the string, but why is that necessary?

> 
> (add-to-list 'org-export-filter-bold-functions 'suvayu-beamer-bold)
> (add-to-list 'org-export-filter-strike-through-functions
>              'suvayu-beamer-structure)
> #+END_SRC
> 
> You can also derive a new back-end from e-beamer that will behave
> differently for bold and strike-through object types.
> 

Thanks a lot for the pointers.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: bold font in org-e-beamer export

[Nicolas Goaziou]

Hello,

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

>> (defun suvayu-beamer-structure (contents backend info)
>>   (if (not (eq backend 'e-beamer)) contents
>>     (replace-regexp-in-string "\\`\\\\[A-Za-z0-9]+" "\\\\structure" contents)))

> But I don't understand the four backslash sequence; I guess it inserts
> \\ to the string, but why is that necessary?

See LITERAL optional argument (which is nil here) in `replace-match'
primitive.


Regards,

-- 
Nicolas Goaziou