Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#21251 - [texlive-core] Cannot use captions in figures and tables with TeXLive 2010's XeTeX
Attached to Project:
Arch Linux
Opened by Evangelos Foutras (foutrelis) - Thursday, 14 October 2010, 14:57 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Wednesday, 20 October 2010, 16:23 GMT
Opened by Evangelos Foutras (foutrelis) - Thursday, 14 October 2010, 14:57 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Wednesday, 20 October 2010, 16:23 GMT
|
DetailsDescription:
The error I receive is "LaTeX Error: Command \nobreakspace unavailable in encoding EU1.". I'm not sure what this means or how it can be fixed. The only reference I could find to this issue is at http://comments.gmane.org/gmane.comp.tex.live/27209. Additional info: * package version(s): texlive-bin 2010.1-4 texlive-core 2010.19888-2 Steps to reproduce: Download attached test case and run the command: `xelatex xetex-caption-test.tex'. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Wednesday, 20 October 2010, 16:23 GMT
Reason for closing: Upstream
Additional comments about closing: Probably an incompatibility due to mixing deprecated packages.
Wednesday, 20 October 2010, 16:23 GMT
Reason for closing: Upstream
Additional comments about closing: Probably an incompatibility due to mixing deprecated packages.
Rémy, are the TeXLive 2010 packages in the repos a "final" release, or sort of like development snapshots?
Regarding this bug, do you think it should be brought to upstream's attention?
So, I'll start using fontspec from now on; feel free to close this bug. :)