Incompatibilities with fontspec package

Issue #29 wontfix
Former user created an issue

``` I’m using TextMate with TexLive 2010 and I get an error when I try to use the fontspec package with “\usepackage”:

\usepackage{fontspec}

The error I get is:

Latex Error: ./ClassicThesis.tex:114 TeX capacity exceeded, sorry [main memory size=3000000].

This is the line with “\part{Some Kind of Manual}”. ```

Original issue reported on code.google.com by `markus.wulftange` on 2011-06-27 17:41:19

Comments (10)

  1. Former user Account Deleted

    ``` I'm not sure if classicthesis can work with XeTeX even without the fontspec package, as some packages in classicthesis-preamble.sty are instructed to use pdftex. May I ask, what do you need fontspec for? The idea of classicthesis style is to use as few fonts as possible, anyhow. ```

    Original issue reported on code.google.com by `ivo.pletikosic` on 2011-06-29 11:16:55 - Labels added: Type-Enhancement - Labels removed: Type-Defect

  2. Former user Account Deleted

    ``` I like the convenience of entering text in UTF-8 directly and using custom fonts. With fontspec it’s quite comfortable to do that. ```

    Original issue reported on code.google.com by `markus.wulftange` on 2011-06-29 11:24:44

  3. André Miede repo owner

    ``` Is it possible to use only classicthesis.sty (w/o the whole template in ClassicThesis.tex etc.) together with fontspec, i.e., using one of the provided example files? ```

    Original issue reported on code.google.com by `amiede` on 2011-07-18 07:26:09

  4. Former user Account Deleted

    ``` Yes, the other examples work when adding “\usepackage{fontspec}” only. ```

    Original issue reported on code.google.com by `markus.wulftange` on 2011-07-19 20:18:31

  5. André Miede repo owner

    ``` That's good news (because classicthesis basically works with fontspec) and bad news (because a change on the manual/template bundle itself will be not done soon because of time constraints and unknown side-effects).

    Hope, you can then use classthesis anyway based on the basic examples. If any adaptation issues arise, contact me via e-mail and please consider sending a postcard. ```

    Original issue reported on code.google.com by `amiede` on 2011-07-21 16:54:32

  6. André Miede repo owner

    ``` (No text was entered with this change) ```

    Original issue reported on code.google.com by `amiede` on 2011-07-21 16:55:22

  7. Former user Account Deleted

    ``` I think it’s the “\spacedlowsmallcaps” that causes this issue in “\Part[2]”. If I remove that, it works like charm (except that the same command is also used in “\Chapter[2]”). Maybe there just needs to be some additional “\protect”-ion or something similar? ```

    Original issue reported on code.google.com by `markus.wulftange` on 2011-07-24 15:24:43

  8. André Miede repo owner

    ``` Hmm, I see. There are different implementations of that command (default/pdf/minion). Could you give it a try using the "pdfspacing" option of classicthesis? ```

    Original issue reported on code.google.com by `amiede` on 2011-07-25 19:47:09

  9. Former user Account Deleted

    ``` André, it seems that \MakeTextUppercase and \MakeTextLowercase in \spaced*caps commads are the source of the problem. In fact (at least in my test case) it's the same with and without the fontspec package. It's all about that XeTeX is having problems with those commands (Markus needs XeTeX for fontspec). I remember I also had some issues with accented characters in headings (you also mention a problem with ß), all because \MakeText*case not behaving properly (are they able to change the case of anything that's not ASCII?)

    ```

    Original issue reported on code.google.com by `ivo.pletikosic` on 2011-07-25 21:18:06

  10. André Miede repo owner

    ``` I just tested it with the "full" template and it still seems to be an issue with the spacing, not the case.

    I.e., without the pdfspacing option, \chapter{Examßäöples}\label{ch:examples} does not work, but using pdfspacing it works (see attachment, chapter 2).

    The ß is still a problem, because it gets converted to "SS" (ß is a lower case letter) but it is not spaced.

    ```

    Original issue reported on code.google.com by `amiede` on 2011-07-26 19:26:56 <hr>

  11. Log in to comment