Using \noboundary as a Text-Command, and similar issues

[ozross]

Hi Heiko.

This cannot be correct, as it redefines a TeX primitive:
.../hyperref/puarenc.def:88:\DeclareTextCommand{\noboundary}{PU}{\9040\015}% U+200D

\documentclass[11pt, oneside]{article}
\usepackage[unicode,arabic,psdextra]{hyperref}
\begin{document}
\noboundary
\end{document}

gives an error:

LaTeX Error: Command \textlozenge unavailable in encoding OT1.

The right way (as I'm sure you know) is something like:
\DeclareTextCommand{\textPUnoboundary}{PU}{\9040\015}% U+200D
with
\let\noboundary\textPUnoboundary
included in \pdfstringdefDisableCommands (or elsewhere) when needed.

Another command showing a similar kind of error is: \textlozenge
when used with packages like: gfsdidot, gfsbodoni, gfsartemisia etc. or drm.sty

\textbullet is another that gets (re)defined in various packages.

Here's another that works smoothly, but results in different output, dependent upon the order in which the packages are loaded.

\documentclass[11pt, oneside]{article}
\usepackage{baskervillef}
\usepackage[unicode]{hyperref}
%\usepackage{baskervillef}
\begin{document}
\textcircled{A}
\end{document}

Then there is the package: ptmxcomp that redefines quite a few \text... macros.

I was hit with similar issues for L8U (pseudo-)encoding, with pdfx.sty.
I've been talking about such issues with Chris, David and Frank. They now realise the importance of pseudo-encodings (as we now call them) such as PU, PD1 and L8U, which are not associated with fonts, but still want to use some of the methods developed for font-encodings.

Cheers,

Ross

[ozross]

Oops, I copied the wrong error message. It should've been:

LaTeX Error: Command \noboundary unavailable in encoding OT1.

Similarly with T1 when packages switch the font encoding.