Mail-Followup-To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
References: <CANQYN6xiwms0LdCgW-6AQ9Pok9qbtc6k0ZgN40z6RK9+a=RdWg@mail.gmail.com>
            <4E945D77.6090309@morningstar2.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Message-ID:  <20111011153219.GA3677@oberdiek.my-fqdn.de>
Date:         Tue, 11 Oct 2011 17:32:19 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Heiko Oberdiek <heiko.oberdiek@GOOGLEMAIL.COM>
Subject: Re: Strings, and regular expressions
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4E945D77.6090309@morningstar2.co.uk>
Precedence: list
Status: R

On Tue, Oct 11, 2011 at 04:15:03PM +0100, Joseph Wright wrote:

> On 10/10/2011 16:07, Bruno Le Floch wrote:
> > - Most encoding functions (as opposed to decoding) could be made
> > expandable. Is it worth it?
> > - There may be need to support other encodings. Which ones?
> > - It is not clear how utf-8 input/output should be treated in pdftex.
> 
> What is needed for PDF bookmark support? This seems to be the main use
> case for these things.

hyperref already reencodes bookmark strings with setting
pdfencoding=auto. The bookmark string is construced in
Unicode encoding. Then the reencoding to PDFDocEncoding is tried.
If successful the result string is used, otherwise the Unicode string.
For the reencoding stuff package stringenc is used and don't need
to be expandable for hyperref.

Yours sincerely
  Heiko Oberdiek