Re: trac 'easyfix' tag

On 05/25/2013 01:58 AM, Pavel Sanda wrote: Given the fact that I can't remember single case that some newcomer started by 'easyfix' bugs during last x years (heh, how many of easyfixes have been targeted by the students applying for GSOC?) I think that this whole discussion is purely academic

changing default output of Hebrew docs to pdflatex

I can now compile all Hebrew documents with both ps2pdf and pdflatex. When I compile with luatex, I get the following error: To avoid this error message, run TeX--XeT or e-TeX engine instead of regular TeX. ! Right-to-Left Support Error: use TeX--XeT or e-TeX engine. l.77 engine} I will

Re: trac 'easyfix' tag

Richard Heck wrote: We do sometimes get people asking about this kind of thing on the list. True, they usually disappear, but perhaps that is because we aren't seen as very responsive. Well, that was the idea behind howto contribute FAQ on web. I felt that many people appear and disappear

Re: make distdir is failing for missing test documents

Stephan Witt wrote: When trying to make a dist tar-ball I get this: make[2]: *** No rule to make target `test/DummyDocument.lyx.lyx', needed by `distdir'. Stop. make[1]: *** [distdir] Error 1 make: *** [distdir] Error 1 This is because tex2lyx does not output the correct files for

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: Still, I think, someone (Jürgen?) should look into this. Into what? The file compiles for me. Jürgen

Re: regression: Chinese tutorial no longer exports (missing babel and language option)

Scott Kostyshak wrote: At commit a78bed06, export of the Chinese Tutorial works fine, but starting with the next commit (a8a2bd46), export is broken again. I think this is because if you export to pdflatex the file has encoding latin1 whereas before it had encoding utf-8. Try again. Jürgen

Re: Re: [LyX master] UserGuide.lyx: first step of revision

Am Samstag, 25. Mai 2013 um 11:39:49, schrieb Jürgen Spitzmüller sp...@lyx.org Kornel Benko wrote: Still, I think, someone (Jürgen?) should look into this. Into what? The file compiles for me. Jürgen It compiles now, because Uwe changed the .lyx file (commit

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: It compiles now, because Uwe changed the .lyx file (commit 57fd14ddf3f60dda9481eaf7c4a91bd8468a3c9a) Before it was not compilable by lyx2.1 (but is compilable by lyx2.06) I get UserGuide.lyx with # git diff -r c42acc7cec9b37edb790fe767fa9e79d4186ca16

Re: Re: [LyX master] UserGuide.lyx: first step of revision

Am Samstag, 25. Mai 2013 um 12:55:17, schrieb Jürgen Spitzmüller sp...@lyx.org Kornel Benko wrote: It compiles now, because Uwe changed the .lyx file (commit 57fd14ddf3f60dda9481eaf7c4a91bd8468a3c9a) Before it was not compilable by lyx2.1 (but is compilable by lyx2.06) I get

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: What I was after, is that this is a regression. The original file is created with 2.0.x, compiles there fine. But after lyx2lyx it does not compile by lyx2.1. I think, it is lyx2lyx problem. I'm not sure this is the case. I cannot imagine lyx2lyx causing anything here. But

Re: changing default output of Hebrew docs to pdflatex

Am 25.05.2013 08:44, schrieb Scott Kostyshak: I can now compile all Hebrew documents with both ps2pdf and pdflatex. When I compile with luatex, I get the following error: To avoid this error message, run TeX--XeT or e-TeX engine instead of regular TeX. ! Right-to-Left Support Error: use

Re: Mac-style paragraph movement

Am 24.05.2013 um 21:07 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 23/05/13 23:51, Stephan Witt a écrit : It jumps to the end of this paragraph here. I've tried the mac-cursor4.diff patch. I tested it with the Users Guide and the Beamer Doc. I'm fine with it. Let's apply it,

Re: [LyX master] UserGuide.lyx: first step of revision

On Sat, May 25, 2013 at 7:18 AM, Jürgen Spitzmüller sp...@lyx.org wrote: But unless we have more backgorund info, we cannot do anything anyway. I did not double check, but it seems believable that the commit that git bisect led me to is indeed the source of the problem here. The commit has to

Re: regression: Chinese tutorial no longer exports (missing babel and language option)

On Sat, May 25, 2013 at 5:49 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: At commit a78bed06, export of the Chinese Tutorial works fine, but starting with the next commit (a8a2bd46), export is broken again. I think this is because if you export to pdflatex the file has

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 12:26 PM, Uwe Stöhr uwesto...@web.de wrote: Am 25.05.2013 08:44, schrieb Scott Kostyshak: I can now compile all Hebrew documents with both ps2pdf and pdflatex. When I compile with luatex, I get the following error: To avoid this error message, run TeX--XeT or e-TeX

Re: lyx2lyx conversion routines (was: Re: #8588: add Sweave Chunk inset)

Dear Richard, I must admit that I'm a bit lost. On Sat, May 25, 2013 at 12:20 AM, Richard Heck rgh...@lyx.org wrote: Try: git apply FILE.patch That should work. The patches are based off 01add2d52f, so you could do: git checkout -b Chunks 01add2d52f first, if you want. I tried to

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

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: lyx2lyx conversion routines

On 05/25/2013 03:54 PM, Liviu Andronic wrote: Dear Richard, I must admit that I'm a bit lost. On Sat, May 25, 2013 at 12:20 AM, Richard Heck rgh...@lyx.org wrote: Try: git apply FILE.patch That should work. The patches are based off 01add2d52f, so you could do: git checkout -b

InsetMathMBox.*

Hi (Georg), for a decade these files are not used and I don't suppose they will be used ever, cf. da92b37c1dac93. So they should go. Scream now or never. Pavel

Re: changing default output of Hebrew docs to pdflatex

Am 25.05.2013 21:42, schrieb Scott Kostyshak: I object. Why do you want to set a certain default? Without a default an engine chosen by the user in his LyX preferences will be used. If he for some reasons we don#t know wants to use ps2pdf, let him do this. You said the following [1]: The

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 7:34 PM, Uwe Stöhr uwesto...@web.de wrote: Am 25.05.2013 21:42, schrieb Scott Kostyshak: Yes, it is. In this case ps2pdf works so we have now several engines that work. LyX's default output format in the preferences is pdflatex and when a user changed this default he

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

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

Re: changing default output of Hebrew docs to pdflatex

Am 26.05.2013 02:24, schrieb Scott Kostyshak: Good point. No, I do not think that would be good. I think that if pdflatex fails, then a default format should definitely be set. If one of the others fails, things are less clear. I think the best thing is to choose a few. Currently we only test

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

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

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

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

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

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

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 9:26 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2013 02:24, schrieb Scott Kostyshak: Good point. No, I do not think that would be good. I think that if pdflatex fails, then a default format should definitely be set. If one of the others fails, things are less

Change or keep Farsi splash.lyx ?

It would be nice to have doc/fa/splash.lyx export correctly as it could be used as a template for someone wanting to write in Farsi. The current splash.lyx file does not compile for me. After reading an email thread [1] and instructions on the wiki [2], I get the attached LyX file, which compiles

Re: Change or keep Farsi splash.lyx ?

Am 26.05.2013 04:47, schrieb Scott Kostyshak: The current splash.lyx file does not compile for me. It compiles fine for me with pdflatex and also XeTeX. (luaTeX of course fails) After reading an email thread [1] and instructions on the wiki [2], I get the attached LyX file, which compiles

JASATex template doesn't work on newest TeX Live 2012

On Ubuntu 12.04 with TeX Live from the PPA, I can compile the JASATeX template just fine. However, I haven't been able to compile the template with the newest TeX Live. I get the following error: ! Undefined control sequence. l.11 \setcitestyle {numbers} % use the numbers

Re: Change or keep Farsi splash.lyx ?

On Sat, May 25, 2013 at 11:15 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2013 04:47, schrieb Scott Kostyshak: The current splash.lyx file does not compile for me. It compiles fine for me with pdflatex and also XeTeX. (luaTeX of course fails) This is good to know. It seems some

Re: Change or keep Farsi splash.lyx ?

Am 26.05.2013 05:22, schrieb Scott Kostyshak: Yes, me. I have written all the Wiki pages about language support. http://wiki.lyx.org/Windows/Farsi (there the Ubuntu section apparently wrong but I cannot correct that as I don't have Ubuntu.) The Ubuntu section is correct. Or rather, it works

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

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

Re: JASATex template doesn't work on newest TeX Live 2012

Am 26.05.2013 05:17, schrieb Scott Kostyshak: On Ubuntu 12.04 with TeX Live from the PPA, I can compile the JASATeX template just fine. However, I haven't been able to compile the template with the newest TeX Live. The differences in the two logs come down to the following (I can post full

Re: Change or keep Farsi splash.lyx ?

On Sat, May 25, 2013 at 11:39 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2013 05:22, schrieb Scott Kostyshak: You could help me and take your existing solution and try to change bit by bit the settings to get the file that we have in master. It cannot be that one needs to set the document

Re: JASATex template doesn't work on newest TeX Live 2012

On Sat, May 25, 2013 at 11:47 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2013 05:17, schrieb Scott Kostyshak: The differences in the two logs come down to the following (I can post full logs if anyone is interested): (good) Package: natbib 2010/09/13 8.31b (PWD, AO) vs. (bad) Package:

Re: JASATex template doesn't work on newest TeX Live 2012

On Sun, May 26, 2013 at 12:02 AM, Scott Kostyshak skost...@lyx.org wrote: On Sat, May 25, 2013 at 11:47 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2013 05:17, schrieb Scott Kostyshak: The differences in the two logs come down to the following (I can post full logs if anyone is

Re: trac 'easyfix' tag

On 05/25/2013 01:58 AM, Pavel Sanda wrote: Given the fact that I can't remember single case that some newcomer started by 'easyfix' bugs during last x years (heh, how many of easyfixes have been targeted by the students applying for GSOC?) I think that this whole discussion is purely academic

changing default output of Hebrew docs to pdflatex

I can now compile all Hebrew documents with both ps2pdf and pdflatex. When I compile with luatex, I get the following error: << To avoid this error message, run TeX--XeT or e-TeX engine instead of regular TeX. ! Right-to-Left Support Error: use TeX--XeT or e-TeX engine. l.77 engine} >> I

Re: trac 'easyfix' tag

Richard Heck wrote: > We do sometimes get people asking about this kind of thing on the list. True, > they usually disappear, but perhaps that is because we aren't seen as very > responsive. Well, that was the idea behind howto contribute FAQ on web. I felt that many people appear and disappear

Re: make distdir is failing for missing test documents

Stephan Witt wrote: > When trying to make a dist tar-ball I get this: > > make[2]: *** No rule to make target `test/DummyDocument.lyx.lyx', needed > by `distdir'. Stop. make[1]: *** [distdir] Error 1 > make: *** [distdir] Error 1 This is because tex2lyx does not output the correct files for

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: > Still, I think, someone (Jürgen?) should look into this. Into what? The file compiles for me. Jürgen

Re: regression: Chinese tutorial no longer exports (missing babel and language option)

Scott Kostyshak wrote: > At commit a78bed06, export of the Chinese Tutorial works fine, but > starting with the next > commit (a8a2bd46), export is broken again. I think this is because if > you export to pdflatex the file has encoding latin1 whereas before it > had encoding utf-8. Try again.

Re: Re: [LyX master] UserGuide.lyx: first step of revision

Am Samstag, 25. Mai 2013 um 11:39:49, schrieb Jürgen Spitzmüller > Kornel Benko wrote: > > Still, I think, someone (Jürgen?) should look into this. > > Into what? The file compiles for me. > > Jürgen It compiles now, because Uwe changed the .lyx file (commit

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: > It compiles now, because Uwe changed the .lyx file (commit > 57fd14ddf3f60dda9481eaf7c4a91bd8468a3c9a) Before it was not compilable by > lyx2.1 (but is compilable by lyx2.06) > > I get UserGuide.lyx with > > # git diff -r c42acc7cec9b37edb790fe767fa9e79d4186ca16 >

Re: Re: [LyX master] UserGuide.lyx: first step of revision

Am Samstag, 25. Mai 2013 um 12:55:17, schrieb Jürgen Spitzmüller > Kornel Benko wrote: > > It compiles now, because Uwe changed the .lyx file (commit > > 57fd14ddf3f60dda9481eaf7c4a91bd8468a3c9a) Before it was not compilable by > > lyx2.1 (but is compilable by lyx2.06) > > > > I

Re: [LyX master] UserGuide.lyx: first step of revision

Kornel Benko wrote: > What I was after, is that this is a regression. The original file is created > with 2.0.x, compiles there fine. But after lyx2lyx it does not compile by > lyx2.1. I think, it is lyx2lyx problem. I'm not sure this is the case. I cannot imagine lyx2lyx causing anything here.

Re: changing default output of Hebrew docs to pdflatex

Am 25.05.2013 08:44, schrieb Scott Kostyshak: I can now compile all Hebrew documents with both ps2pdf and pdflatex. When I compile with luatex, I get the following error: << To avoid this error message, run TeX--XeT or e-TeX engine instead of regular TeX. ! Right-to-Left Support Error: use

Re: Mac-style paragraph movement

Am 24.05.2013 um 21:07 schrieb Jean-Marc Lasgouttes : > Le 23/05/13 23:51, Stephan Witt a écrit : >> It jumps to the end of this paragraph here. >> >> I've tried the mac-cursor4.diff patch. I tested it with the Users Guide and >> the Beamer Doc. >> I'm fine with it. > >

Re: [LyX master] UserGuide.lyx: first step of revision

On Sat, May 25, 2013 at 7:18 AM, Jürgen Spitzmüller wrote: > But unless we have more backgorund info, we cannot do anything anyway. I did not double check, but it seems believable that the commit that git bisect led me to is indeed the source of the problem here. The commit has

Re: regression: Chinese tutorial no longer exports (missing babel and language option)

On Sat, May 25, 2013 at 5:49 AM, Jürgen Spitzmüller wrote: > Scott Kostyshak wrote: >> At commit a78bed06, export of the Chinese Tutorial works fine, but >> starting with the next >> commit (a8a2bd46), export is broken again. I think this is because if >> you export to pdflatex the

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 12:26 PM, Uwe Stöhr wrote: > Am 25.05.2013 08:44, schrieb Scott Kostyshak: > >> I can now compile all Hebrew documents with both ps2pdf and pdflatex. >> When I compile with luatex, I get the following error: >> >> << >> To avoid this error message, >> run

Re: lyx2lyx conversion routines (was: Re: #8588: add Sweave Chunk inset)

Dear Richard, I must admit that I'm a bit lost. On Sat, May 25, 2013 at 12:20 AM, Richard Heck wrote: > Try: > git apply FILE.patch > That should work. The patches are based off 01add2d52f, so you could do: > git checkout -b Chunks 01add2d52f > first, if you want. > I

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

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.

Re: lyx2lyx conversion routines

On 05/25/2013 03:54 PM, Liviu Andronic wrote: Dear Richard, I must admit that I'm a bit lost. On Sat, May 25, 2013 at 12:20 AM, Richard Heck wrote: Try: git apply FILE.patch That should work. The patches are based off 01add2d52f, so you could do: git checkout -b

InsetMathMBox.*

Hi (Georg), for a decade these files are not used and I don't suppose they will be used ever, cf. da92b37c1dac93. So they should go. Scream now or never. Pavel

Re: changing default output of Hebrew docs to pdflatex

Am 25.05.2013 21:42, schrieb Scott Kostyshak: I object. Why do you want to set a certain default? Without a default an engine chosen by the user in his LyX preferences will be used. If he for some reasons we don#t know wants to use ps2pdf, let him do this. You said the following [1]: "The

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 7:34 PM, Uwe Stöhr wrote: > Am 25.05.2013 21:42, schrieb Scott Kostyshak: > > Yes, it is. In this case ps2pdf works so we have now several engines that > work. LyX's default output format in the preferences is pdflatex and when a > user changed this

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

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

Re: changing default output of Hebrew docs to pdflatex

Am 26.05.2013 02:24, schrieb Scott Kostyshak: Good point. No, I do not think that would be good. I think that if pdflatex fails, then a default format should definitely be set. If one of the others fails, things are less clear. I think the best thing is to choose a few. Currently we only test

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

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

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

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

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

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. > > >>

Re: changing default output of Hebrew docs to pdflatex

On Sat, May 25, 2013 at 9:26 PM, Uwe Stöhr wrote: > Am 26.05.2013 02:24, schrieb Scott Kostyshak: > > >> Good point. No, I do not think that would be good. I think that if >> pdflatex fails, then a default format should definitely be set. If one >> of the others fails, things

Change or keep Farsi splash.lyx ?

It would be nice to have doc/fa/splash.lyx export correctly as it could be used as a template for someone wanting to write in Farsi. The current splash.lyx file does not compile for me. After reading an email thread [1] and instructions on the wiki [2], I get the attached LyX file, which compiles

Re: Change or keep Farsi splash.lyx ?

Am 26.05.2013 04:47, schrieb Scott Kostyshak: The current splash.lyx file does not compile for me. It compiles fine for me with pdflatex and also XeTeX. (luaTeX of course fails) After reading an email thread [1] and instructions on the wiki [2], I get the attached LyX file, which compiles

JASATex template doesn't work on newest TeX Live 2012

On Ubuntu 12.04 with TeX Live from the PPA, I can compile the JASATeX template just fine. However, I haven't been able to compile the template with the newest TeX Live. I get the following error: ! Undefined control sequence. l.11 \setcitestyle {numbers} % use the numbers

Re: Change or keep Farsi splash.lyx ?

On Sat, May 25, 2013 at 11:15 PM, Uwe Stöhr wrote: > Am 26.05.2013 04:47, schrieb Scott Kostyshak: > > >> The current splash.lyx file does not compile for me. > > > It compiles fine for me with pdflatex and also XeTeX. (luaTeX of course > fails) This is good to know. It seems

Re: Change or keep Farsi splash.lyx ?

Am 26.05.2013 05:22, schrieb Scott Kostyshak: Yes, me. I have written all the Wiki pages about language support. http://wiki.lyx.org/Windows/Farsi (there the Ubuntu section apparently wrong but I cannot correct that as I don't have Ubuntu.) The Ubuntu section is correct. Or rather, it works

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

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

Re: JASATex template doesn't work on newest TeX Live 2012

Am 26.05.2013 05:17, schrieb Scott Kostyshak: On Ubuntu 12.04 with TeX Live from the PPA, I can compile the JASATeX template just fine. However, I haven't been able to compile the template with the newest TeX Live. The differences in the two logs come down to the following (I can post full

Re: Change or keep Farsi splash.lyx ?

On Sat, May 25, 2013 at 11:39 PM, Uwe Stöhr wrote: > Am 26.05.2013 05:22, schrieb Scott Kostyshak: > > You could help me and take your existing solution and try to change bit by > bit the settings to get the file that we have in master. It cannot be that > one needs to set the

Re: JASATex template doesn't work on newest TeX Live 2012

On Sat, May 25, 2013 at 11:47 PM, Uwe Stöhr wrote: > Am 26.05.2013 05:17, schrieb Scott Kostyshak: > >> The differences in the two logs come down to the following (I can post >> full logs if anyone is interested): >> (good) Package: natbib 2010/09/13 8.31b (PWD, AO) >> vs. >>

Re: JASATex template doesn't work on newest TeX Live 2012

On Sun, May 26, 2013 at 12:02 AM, Scott Kostyshak wrote: > On Sat, May 25, 2013 at 11:47 PM, Uwe Stöhr wrote: >> Am 26.05.2013 05:17, schrieb Scott Kostyshak: >> >>> The differences in the two logs come down to the following (I can post >>> full logs if anyone