Re: Bug in org-latex (6.34c)?

[Carsten Dominik <dominik@uva.nl>]

On Jan 24, 2010, at 10:55 AM, Carsten Dominik wrote:

>
> On Jan 24, 2010, at 12:26 AM, Sven Bretfeld wrote:
>
>> Hi Carsten
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> This works for me:
>>>
>>> (setq org-export-latex-inputenc-alist '(("utf8" . "utf8x)))
>>
>> Yes, that's working. Thank you very much.
>>
>>> Is this what you have?
>>
>> I set that function via customize. I think there was only one set og
>> parenthesis.
>>
>>> I can make a variable to turn this automatic fixing of inputenc  
>>> off, so
>>> that the configured value in org-export-latex-classes will always be
>>> used....
>>
>> So, it's not a bug, it'a a feature. At least it should be  
>> documented in
>> a more accessible place. All the predefined export classes contain  
>> the
>> \usepackage[utf8]{inputenc} header. This suggests that having that  
>> line
>> or changing it would have any effect.
>
> Maybe we should redefine the classes to use
>
> \usepackage[BUFFERCODING]{inputenc}
>
> and the only modify the coding system if it is the special value  
> BUFFERCODING, but not if the user has specified one explicitly......

OK, when I can push next, it will work like this:

When the class defines

\usepackage[AUTO]{inputenc}

then Org will set the coding system automatically.  If the class  
specifies
an explicit coding system like

\usepackage[utf8]{inputenc}

it will be left alone.  This is a lot more predictable that what
I had before, thanks for making me change this.

- Carsten


>
> - Carsten
>
>>
>> Thanks again and greetings,
>>
>> Sven
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>
>

- Carsten