textcomp Error: symbol \textuparrow not provided by
Having just added a symbol up-arrow, every time I build my PDF, Lyx
gives this error:
textcomp Error: symbol \textuparrow not provided by
("by" is the last word of the error)
althought the PDF displays the arrow just fine.
The arrow is in a LyxCode environment, but further testing shows that it
just hates doing an up-arrow within \ttfamily
as it works anyway, any tips to stop it complaining?
Sam
Re: textcomp Error: symbol \textuparrow not provided by
Sam Liddicott schrieb:
Having just added a symbol up-arrow, every time I build my PDF, Lyx
gives this error:
textcomp Error: symbol \textuparrow not provided by
("by" is the last word of the error)
Can you please provide a _small_ LyX example file?
regards Uwe
Re: textcomp Error: symbol \textuparrow not provided by
* Uwe Stöhr wrote, On 10/11/09 17:32:
Sam Liddicott schrieb:
Having just added a symbol up-arrow, every time I build my PDF, Lyx
gives this error:
textcomp Error: symbol \textuparrow not provided by
("by" is the last word of the error)
Can you please provide a _small_ LyX example file?
It seems to be a conflict with luximono
Sam
t1.lyx
Description: application/lyx
Re: textcomp Error: symbol \textuparrow not provided by
On 2009-11-11, Sam Liddicott wrote:
> --060501010505080308020304
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 8bit
> * Uwe Stöhr wrote, On 10/11/09 17:32:
>> Sam Liddicott schrieb:
>>> Having just added a symbol up-arrow, every time I build my PDF, Lyx
>>> gives this error:
>>> textcomp Error: symbol \textuparrow not provided by
>>> ("by" is the last word of the error)
This seems to be a bug in LyX's log parser truncating the remainder of the
error message.
>> Can you please provide a _small_ LyX example file?
> It seems to be a conflict with luximono
Rather a limitation of luximono (not providing a symbol for \textuparrow).
Did you look at Document>LaTeX log to find the full error and its context?
As a substitution is found, maybe it should be reported as warning instead
of error (either upstream by textcomp or as a workaround in LyX).
Günter
Re: textcomp Error: symbol \textuparrow not provided by
Sam Liddicott schrieb: Having just added a symbol up-arrow, every time I build my PDF, Lyx gives this error: textcomp Error: symbol \textuparrow not provided by It seems to be a conflict with luximono The luximono font does not yet provide a glyph for the uparrow character. It would be nice if you could report this to the luximono developers. Perhaps the next version of the luximono fonts will then contain some more glyphs. For now, you need to use another font, for example Latin Modern Typewriter. regards Uwe
Re: textcomp Error: symbol \textuparrow not provided by
* Uwe Stöhr wrote, On 11/11/09 14:08: Sam Liddicott schrieb: Having just added a symbol up-arrow, every time I build my PDF, Lyx gives this error: textcomp Error: symbol \textuparrow not provided by It seems to be a conflict with luximono The luximono font does not yet provide a glyph for the uparrow character. It would be nice if you could report this to the luximono developers. Perhaps the next version of the luximono fonts will then contain some more glyphs. For now, you need to use another font, for example Latin Modern Typewriter. Thanks for the tip. I will report it. I find it interesting that the up-arrow still rendered, but that the error stopped lyx's latex run (and second run to resolve references). It seems like latex or lyx half works around this. Sam
Re: textcomp Error: symbol \textuparrow not provided by
Sam Liddicott schrieb: I find it interesting that the up-arrow still rendered, but that the error stopped lyx's latex run (and second run to resolve references). This is the correct behaviour: When a LaTeX-error occurs, LyX stops because LaTeX stops. That this raises a LaTeX error instead of a LaTeX warning is another issue of the luximono fonts. regards Uwe
Re: textcomp Error: symbol \textuparrow not provided by
* Uwe Stöhr wrote, On 11/11/09 15:16:
Sam Liddicott schrieb:
I find it interesting that the up-arrow still rendered, but that the
error stopped lyx's latex run (and second run to resolve references).
This is the correct behaviour: When a LaTeX-error occurs, LyX stops
because LaTeX stops. That this raises a LaTeX error instead of a LaTeX
warning is another issue of the luximono fonts.
Fair enough.
I did submit a report to Bigelow and Holmes about luxi-mono.
I suppose another fix would be a package that redefines \textuparrow{}
(etc) to switch font if running under the ul9 font.
I'll try and work out how to do that.
Sam
Re: textcomp Error: symbol \textuparrow not provided by
On 2009-11-12, Sam Liddicott wrote:
> * Uwe Stöhr wrote, On 11/11/09 15:16:
>> Sam Liddicott schrieb:
> I suppose another fix would be a package that redefines \textuparrow{}
> (etc) to switch font if running under the ul9 font.
Redefining \textuparrow would only be a workaround, no fix.
The standard behaviour is: if the symbol is not available in the
font, a replacement is used from a different font and a warning issued.
This also works in your example (as you reported). However instead of
the common Warning, an Error is thrown -- this is the problem.
Günter
