|
From: Ulrike F. <li...@ni...> - 2011-05-08 11:28:50
|
Am Sun, 08 May 2011 10:33:35 +0100 schrieb José Carlos Santos: >>> I've had some problems lately with the MiKTeX fonts in one of my >>> computers and I decided to uninstall MiKTeX and to re-install it. It >>> failed. When I was trying to re-install, I got this error message: >>> fc-cache.EXE: >>> Windows API error 1113: No mapping for the Unicode character exists in >>> the target multi-byte code page. >>> Any ideas? >> >> Well as I already wrote in a comment to your bug report: >> >> "Regarding the fc-cache error: Try to run fc-cache --verbose. >> Perhaps this tells you if fc-cache doesn't like a configuration >> entry. > > If I do that then I get the message "fc-cache: Windows API error 1113: > No mapping for the Unicode character exists in the target multi-byte > code page." > >> (My guess is that you are using accented chars in your user >> name.)" > > No, I am not. And I am not using spaces either. I have seen this message previously (e.g in the bug report ID 3198946) and while there isn't a decisive proof yet I got the impression that it related to localized windows of languages with "accents" (the bug report eg is from a french). Find in the UserConfig or CommonConfig root in fontconfig/config the .conf files (fonts.conf, localfonts.conf etc). Check if they contain pathes with non-ASCII-chars. Try out if fc-cache works if you uncomment such pathes. Another possibility where non-ASCII-chars can "intrude" are your fonts. Try to remove from localfonts.conf the system font folder. (Make backups of the files before starting to change them). -- Ulrike Fischer |