Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-26 Thread Uwe Stöhr

Am 26.05.2013 05:42, schrieb Uwe Stöhr:


This works for this special file but will of course fail when you use e.g. an 
umlaut in the text. So
it turned out that adding latin9 to the document class options is indeed the 
proper solution.
Maybe we should add this by default in the layout file - I'll investigate this.


Here is the analysis:

- the major problem of AA is that it comes with an outdated version of natbib.sty and that this 
version is customized for the needs of AA. This leads to many problems because LaTeX might use this 
natbib for other files so that other documents can become uncompilable (as we have seen with JASA). 
Unfortunately one cannot use for AA the unmodified natbib from CTAN

Result:
 - I removed the manual bibliography and used in the example file BibTeX
 - I mentioned in the layout file that AA loads natbib by default so that you don't get 
compilation errors when setting natbib in the document settings


- AA always loads inputenc with the option utf8. To get additional encodings, AA provides the the 
class options ascii, latin1 and latin9. This is problematic if e.g. the author name of a paper 
contains a Vietnamese character. But OK, that is the decision of AA

Result:
 - I predefined the option latin9 in the layout file and added a note in the template and example 
file that this option should be used for accented characters


regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-26 Thread Scott Kostyshak
On Sun, May 26, 2013 at 12:14 PM, Uwe Stöhr uwesto...@web.de wrote:
 Am 26.05.2013 05:42, schrieb Uwe Stöhr:


 This works for this special file but will of course fail when you use e.g.
 an umlaut in the text. So
 it turned out that adding latin9 to the document class options is indeed
 the proper solution.
 Maybe we should add this by default in the layout file - I'll investigate
 this.


 Here is the analysis:

 - the major problem of AA is that it comes with an outdated version of
 natbib.sty and that this version is customized for the needs of AA. This
 leads to many problems because LaTeX might use this natbib for other files
 so that other documents can become uncompilable (as we have seen with JASA).
 Unfortunately one cannot use for AA the unmodified natbib from CTAN
 Result:
  - I removed the manual bibliography and used in the example file BibTeX
  - I mentioned in the layout file that AA loads natbib by default so that
 you don't get compilation errors when setting natbib in the document
 settings

 - AA always loads inputenc with the option utf8. To get additional
 encodings, AA provides the the class options ascii, latin1 and
 latin9. This is problematic if e.g. the author name of a paper contains a
 Vietnamese character. But OK, that is the decision of AA
 Result:
  - I predefined the option latin9 in the layout file and added a note in
 the template and example file that this option should be used for accented
 characters

Sounds like you did everything you could to make up for this strange situation.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-26 Thread Uwe Stöhr

Am 26.05.2013 05:42, schrieb Uwe Stöhr:


This works for this special file but will of course fail when you use e.g. an 
umlaut in the text. So
it turned out that adding "latin9" to the document class options is indeed the 
proper solution.
Maybe we should add this by default in the layout file - I'll investigate this.


Here is the analysis:

- the major problem of A is that it comes with an outdated version of natbib.sty and that this 
version is customized for the needs of A This leads to many problems because LaTeX might use this 
natbib for other files so that other documents can become uncompilable (as we have seen with JASA). 
Unfortunately one cannot use for A the unmodified natbib from CTAN

Result:
 - I removed the manual bibliography and used in the example file BibTeX
 - I mentioned in the layout file that A loads natbib by default so that you don't get 
compilation errors when setting natbib in the document settings


- A always loads inputenc with the option utf8. To get additional encodings, A provides the the 
class options "ascii", "latin1" and "latin9". This is problematic if e.g. the author name of a paper 
contains a Vietnamese character. But OK, that is the decision of A

Result:
 - I predefined the option "latin9" in the layout file and added a note in the template and example 
file that this option should be used for accented characters


regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-26 Thread Scott Kostyshak
On Sun, May 26, 2013 at 12:14 PM, Uwe Stöhr  wrote:
> Am 26.05.2013 05:42, schrieb Uwe Stöhr:
>
>
>> This works for this special file but will of course fail when you use e.g.
>> an umlaut in the text. So
>> it turned out that adding "latin9" to the document class options is indeed
>> the proper solution.
>> Maybe we should add this by default in the layout file - I'll investigate
>> this.
>
>
> Here is the analysis:
>
> - the major problem of A is that it comes with an outdated version of
> natbib.sty and that this version is customized for the needs of A This
> leads to many problems because LaTeX might use this natbib for other files
> so that other documents can become uncompilable (as we have seen with JASA).
> Unfortunately one cannot use for A the unmodified natbib from CTAN
> Result:
>  - I removed the manual bibliography and used in the example file BibTeX
>  - I mentioned in the layout file that A loads natbib by default so that
> you don't get compilation errors when setting natbib in the document
> settings
>
> - A always loads inputenc with the option utf8. To get additional
> encodings, A provides the the class options "ascii", "latin1" and
> "latin9". This is problematic if e.g. the author name of a paper contains a
> Vietnamese character. But OK, that is the decision of A
> Result:
>  - I predefined the option "latin9" in the layout file and added a note in
> the template and example file that this option should be used for accented
> characters

Sounds like you did everything you could to make up for this strange situation.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak skost...@lyx.org wrote:
 Exporting with luatex works fine. With pdflatex and ps2pdf I get an
 inputenc option clash.

 Is there a fix?

Adding 'latin9' as a class option fixes compilation for me. I will
commit this unless someone objects.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 25.05.2013 21:58, schrieb Scott Kostyshak:


On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak skost...@lyx.org wrote:

Exporting with luatex works fine. With pdflatex and ps2pdf I get an
inputenc option clash.

Is there a fix?


Adding 'latin9' as a class option fixes compilation for me. I will
commit this unless someone objects.


Scott I appreciate your work and you uncover some problems. But why do you want to hide the bugs you 
just uncovered?


The support for aa was updated the last time 5 years ago. The latest aa class loads now already the 
package inputenc so that you got an option clash for inputenc. So the fix was to update the layout file.


regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sat, May 25, 2013 at 9:13 PM, Uwe Stöhr uwesto...@web.de wrote:
 Am 25.05.2013 21:58, schrieb Scott Kostyshak:


 On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak skost...@lyx.org wrote:

 Exporting with luatex works fine. With pdflatex and ps2pdf I get an
 inputenc option clash.

 Is there a fix?


 Adding 'latin9' as a class option fixes compilation for me. I will
 commit this unless someone objects.


 Scott I appreciate your work and you uncover some problems. But why do you
 want to hide the bugs you just uncovered?

Because of ignorance :). It is never my intention to hide a bug. I
first asked if someone knew how to fix the bug. No one responded so I
started experimenting. I found something that worked for me and
reported back to the list. This led you to the correct solution. This
was a success in my opinion.

 The support for aa was updated the last time 5 years ago. The latest aa
 class loads now already the package inputenc so that you got an option clash
 for inputenc. So the fix was to update the layout file.

Thank you for fixing it.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 26.05.2013 03:27, schrieb Scott Kostyshak:


Scott I appreciate your work and you uncover some problems. But why do you
want to hide the bugs you just uncovered?


I should have added a smiley here.


Because of ignorance :). It is never my intention to hide a bug.


I know; that was meant with an ;-)

regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sat, May 25, 2013 at 9:30 PM, Uwe Stöhr uwesto...@web.de wrote:
 Am 26.05.2013 03:27, schrieb Scott Kostyshak:


 Scott I appreciate your work and you uncover some problems. But why do
 you
 want to hide the bugs you just uncovered?


 I should have added a smiley here.


 Because of ignorance :). It is never my intention to hide a bug.


 I know; that was meant with an ;-)

A retroactive smiley does the job just as well :)

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 26.05.2013 03:13, schrieb Uwe Stöhr:


The support for aa was updated the last time 5 years ago. The latest aa class 
loads now already the
package inputenc so that you got an option clash for inputenc. So the fix was 
to update the layout
file.


This works for this special file but will of course fail when you use e.g. an umlaut in the text. So 
it turned out that adding latin9 to the document class options is indeed the proper solution. 
Maybe we should add this by default in the layout file - I'll investigate this.


regards Uwe



Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak  wrote:
> Exporting with luatex works fine. With pdflatex and ps2pdf I get an
> inputenc option clash.
>
> Is there a fix?

Adding 'latin9' as a class option fixes compilation for me. I will
commit this unless someone objects.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 25.05.2013 21:58, schrieb Scott Kostyshak:


On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak  wrote:

Exporting with luatex works fine. With pdflatex and ps2pdf I get an
inputenc option clash.

Is there a fix?


Adding 'latin9' as a class option fixes compilation for me. I will
commit this unless someone objects.


Scott I appreciate your work and you uncover some problems. But why do you want to hide the bugs you 
just uncovered?


The support for aa was updated the last time 5 years ago. The latest aa class loads now already the 
package inputenc so that you got an option clash for inputenc. So the fix was to update the layout file.


regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sat, May 25, 2013 at 9:13 PM, Uwe Stöhr  wrote:
> Am 25.05.2013 21:58, schrieb Scott Kostyshak:
>
>
>> On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak  wrote:
>>>
>>> Exporting with luatex works fine. With pdflatex and ps2pdf I get an
>>> inputenc option clash.
>>>
>>> Is there a fix?
>>
>>
>> Adding 'latin9' as a class option fixes compilation for me. I will
>> commit this unless someone objects.
>
>
> Scott I appreciate your work and you uncover some problems. But why do you
> want to hide the bugs you just uncovered?

Because of ignorance :). It is never my intention to hide a bug. I
first asked if someone knew how to fix the bug. No one responded so I
started experimenting. I found something that worked for me and
reported back to the list. This led you to the correct solution. This
was a success in my opinion.

> The support for aa was updated the last time 5 years ago. The latest aa
> class loads now already the package inputenc so that you got an option clash
> for inputenc. So the fix was to update the layout file.

Thank you for fixing it.

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 26.05.2013 03:27, schrieb Scott Kostyshak:


Scott I appreciate your work and you uncover some problems. But why do you
want to hide the bugs you just uncovered?


I should have added a smiley here.


Because of ignorance :). It is never my intention to hide a bug.


I know; that was meant with an ;-)

regards Uwe


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Scott Kostyshak
On Sat, May 25, 2013 at 9:30 PM, Uwe Stöhr  wrote:
> Am 26.05.2013 03:27, schrieb Scott Kostyshak:
>
>
>>> Scott I appreciate your work and you uncover some problems. But why do
>>> you
>>> want to hide the bugs you just uncovered?
>
>
> I should have added a smiley here.
>
>
>> Because of ignorance :). It is never my intention to hide a bug.
>
>
> I know; that was meant with an ;-)

A retroactive smiley does the job just as well :)

Scott


Re: templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf

2013-05-25 Thread Uwe Stöhr

Am 26.05.2013 03:13, schrieb Uwe Stöhr:


The support for aa was updated the last time 5 years ago. The latest aa class 
loads now already the
package inputenc so that you got an option clash for inputenc. So the fix was 
to update the layout
file.


This works for this special file but will of course fail when you use e.g. an umlaut in the text. So 
it turned out that adding "latin9" to the document class options is indeed the proper solution. 
Maybe we should add this by default in the layout file - I'll investigate this.


regards Uwe