Re: [Docutils-users] latex writers: textuparrow question

[Guenter M. <mi...@us...>]

On 2010-09-19, Alan G Isaac wrote:
> On 9/18/2010 8:32 AM, Guenter Milde wrote:

Your reported a textcomp error.

>> Did you try the proposed workarounds?

> You pointed me to
> http://docutils.sourceforge.net/docs/user/latex.html#error-symbol-textcurrency-not-provided

> What I see as proposed workarounds (for a related but not identical
> problem) are:

>      Add either
>      warn:	turn the error in a warning, use the default symbol (bitmap), or
>      force,almostfull:	use the symbol provided by the font at the users risk,

>      to the document options or use a different font package.

> I take it this means something like ::

>      --documentoptions=warn

> or ::

>      --documentoptions=force,almostfull

Yes.

> But these are not (I think??) standard LaTeX documentclass
> options.  They look to be textcomp options.  (Can you point
> to some useful discussion of what they do?  Sorry for my
> failed web-fu.)  

They are. I suggest the textcomp documentation as further reading.

> But doing the above will provide these
> as document-wide options, not just to the textcomp package.
> Is that safe? 

This depends on what other packages you load and if these will
(mis)interpret the global options.
See clsguide.pdf (`textdoc clsguide`) for details.

> Is it possible to provide package specific
> options?

Only with \PassOptionsToPackage{warn}{textcomp} in a custom template file
or a custom front-end.

> But to answer your question: if I set ``warn`` as a document
> option, textcomp errors become just warnings, and the
> document correctly compiles without stopping.

Did you check, if the textuparrow glyph matches the rest of the document?

Remember, the above is a *workaround*. The solution is to use a font that
provides the glyph.

Günter