On 2016-02-23, Kornel Benko wrote:
> Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde 
> <mi...@users.sf.net>
>> On 2016-02-20, Guenter Milde wrote:
>> > On 2016-02-20, Kornel Benko wrote:
>> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
>> >> <mi...@users.sf.net>

>> Dear Kornel, 

...
>> >>> >> > I installed fonts-font-awesome, now the font is found. 

>> ... it is loaded in the tex output -- however, this is due to the
>> line

>> #  
>> \DeclareLaTeXClass[moderncv,ebgaramond.sty,fancyhdr.sty,fontawesome.sty,ifpdf.sty,marvosym.sty]{Modern
>>  CV}

>> in moderncv.layout.

>> The edit of the example "unearthed" a dependency problem with
>> moderncv.layout that can occure when

>> * compiling with XeTeX,
>> * fonts awesome installed for LaTeX but not declared a system font. 

>> See answer 2 in 
>> http://tex.stackexchange.com/questions/132888/fontawesome-font-not-found

> I have different problem with xelatex. The 'broken' example in this
> link compiles fine here, so xelatex finds the font already.

Maybe a different version as system font and TeX font?

>> >>> >> > But there are still missing glyphs.
>> ...
>> >>> > Output of xelatex (system font + tex font):
>> >>> > Missing character: There is no  in font FontAwesome/OT!

>> > Do you mean the literal character between "no" and "in font"?

>> > My editor says this is:

>> > Character '' (61868, 0xF1AC)

>> > which is in:

>> > @@ E000    Private Use Area        F8FF
>> > @+         This range of 6400 code points is dedicated to private use.

>> It is actually a non-standard character in the private use area:

>>   Font Awesome is a free (CC-BY-3.0) icon font from GitHub, that contains
>>   several different icons for various purposes. It is designed for web
>>   usage, and thus all the characters are defined in the private unicode
>>   range to avoid confusing screen readers.

>>   -- https://coderwall.com/p/r67dyq/using-font-awesome-with-xe-latex

>> I am not sure whether this is a good idea, but here you are...

> I don't understand. 

This was an aside: I don't know whether it is a good idea to create a font
with all characters in the private use area, but this is what the designers
of "Awesome" did. The moderncv author seems to like the idea (or just the
font) and hence used it in the package...



> I already have the newest fontawesome.sty in TL, so no need to add it to
> some project dir.

While pdftex uses a local, customized 8-bit encoded version of the font
and luatex uses the version installed by TL via its own font loading
mechanism, XeTeX loads fonts via the OS.

Could you check with some font listing program or LibreOffice or similar,
whether the missing character is present in the font "as seen by the system"?


Otherwise, if you cannot solve this problem, I suggest to add a pattern
for the test(s) that fail at your site to unreliableTests with a telling
comment.

Günter




Günter

Reply via email to