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: 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: 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: 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: regression: Chinese tutorial no longer exports (missing babel and language option)

On Mon, May 20, 2013 at 5:08 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: The commit that git bisect lead me to and the diff between the pdflatex .tex files of before and after the following commit (which is the same as the diff between the output from before and current

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

On Mon, May 20, 2013 at 5:08 AM, Jürgen Spitzmüller wrote: > Scott Kostyshak wrote: >> The commit that git bisect lead me to and the diff between the >> pdflatex .tex files of before and after the following commit (which is >> the same as the diff between the output from before and

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

Scott Kostyshak wrote: The commit that git bisect lead me to and the diff between the pdflatex .tex files of before and after the following commit (which is the same as the diff between the output from before and current trunk) is pasted below. After adding the English class option and adding

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

Scott Kostyshak wrote: > The commit that git bisect lead me to and the diff between the > pdflatex .tex files of before and after the following commit (which is > the same as the diff between the output from before and current trunk) > is pasted below. After adding the English class option and

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

The commit that git bisect lead me to and the diff between the pdflatex .tex files of before and after the following commit (which is the same as the diff between the output from before and current trunk) is pasted below. After adding the English class option and adding babel to the preamble, the

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

The commit that git bisect lead me to and the diff between the pdflatex .tex files of before and after the following commit (which is the same as the diff between the output from before and current trunk) is pasted below. After adding the English class option and adding babel to the preamble, the

Re: Language option

On Tue, Feb 13, 2001 at 07:38:00PM +0200, Dekel Tsur wrote: On Tue, Feb 13, 2001 at 06:30:01PM +, Herbert Voss wrote: What we can do is either 1) Put a "do not use babel" button in the document dialog or 2) Put a "do not use babel" button and in the

Re: Language option

On Tue, Feb 13, 2001 at 07:38:00PM +0200, Dekel Tsur wrote: > On Tue, Feb 13, 2001 at 06:30:01PM +, Herbert Voss wrote: > > >What we can do is either > > >1) Put a "do not use babel" button in the document dialog > > > or > > > 2) Put a "do not use babel" button and in

Language option

from my point of view it's no more possible to prevent lyx from choosing a language for documentclass["any language",... it will be a good idea, if an option "no language" appears as first in the list. In this case lyx may choose no language in documentclass ... Herbert -- [EMAIL

RE: Language option

On 13-Feb-2001 Herbert Voss wrote: it will be a good idea, if an option "no language" appears as first in the list. In this case lyx may choose no language in documentclass ... That would be the same as the "default" language we had earlier and we removed for reasons already discussed quite

Re: Language option

On Tue, Feb 13, 2001 at 06:30:01PM +, Herbert Voss wrote: What we can do is either 1) Put a "do not use babel" button in the document dialog or 2) Put a "do not use babel" button and in the preferences dialog, and if this button is selected, babel will

Language option

from my point of view it's no more possible to prevent lyx from choosing a language for documentclass["any language",... it will be a good idea, if an option "no language" appears as first in the list. In this case lyx may choose no language in documentclass ... Herbert -- [EMAIL

RE: Language option

On 13-Feb-2001 Herbert Voss wrote: > it will be a good idea, if an option "no language" appears > as first in the list. In this case lyx may choose no language > in documentclass ... That would be the same as the "default" language we had earlier and we removed for reasons already discussed

Re: Language option

On Tue, Feb 13, 2001 at 06:30:01PM +, Herbert Voss wrote: > >What we can do is either > >1) Put a "do not use babel" button in the document dialog > > or > > 2) Put a "do not use babel" button and in the preferences dialog, > > and if this button is selected,

Re: A bug/fix report for language option in LyX1.1.6fix1

Thanks. A new version of hyperref solves the problem. But putting the language as a global option does break some other packages, for example, the newest slide making package "prosper" will be broken if the global language option is used. Does it make more sense that the langu

Re: A bug/fix report for language option in LyX1.1.6fix1

On Fri, Feb 09, 2001 at 08:49:49AM -0500, Min Xu wrote: Thanks. A new version of hyperref solves the problem. But putting the language as a global option does break some other packages, for example, the newest slide making package "prosper" will be broken if the global langu

Re: A bug/fix report for language option in LyX1.1.6fix1

Min Xu [EMAIL PROTECTED] writes: | Thanks. A new version of hyperref solves the problem. But putting the language | as a global option does break some other packages, for example, the newest | slide making package "prosper" will be broken if the global language option

Re: A bug/fix report for language option in LyX1.1.6fix1

Thanks. A new version of hyperref solves the problem. But putting the language as a global option does break some other packages, for example, the newest slide making package "prosper" will be broken if the global language option is used. Does it make more sense that the langu

Re: A bug/fix report for language option in LyX1.1.6fix1

On Fri, Feb 09, 2001 at 08:49:49AM -0500, Min Xu wrote: > Thanks. A new version of hyperref solves the problem. But putting the language > as a global option does break some other packages, for example, the newest > slide making package "prosper" will be broken if the glo

Re: A bug/fix report for language option in LyX1.1.6fix1

Min Xu <[EMAIL PROTECTED]> writes: | Thanks. A new version of hyperref solves the problem. But putting the language | as a global option does break some other packages, for example, the newest | slide making package "prosper" will be broken if the global language o

A bug/fix report for language option in LyX1.1.6fix1

Hi, The LyX1.1.6fix1 handles the language option by putting it as a global option. Recently, I found this placement make the pdflatex fail with the following message: ! LaTeX Error: Missing \begin{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H return

Re: A bug/fix report for language option in LyX1.1.6fix1

Min Xu [EMAIL PROTECTED] writes: | Hi, | | The LyX1.1.6fix1 handles the language option by putting it as a global | option. Recently, I found this placement make the pdflatex fail with | the following message: If so, this is a bug in pdflatex or the documentclass or a package file... Can you

Re: A bug/fix report for language option in LyX1.1.6fix1

On Thu, Feb 08, 2001 at 10:05:28AM -0500, Min Xu wrote: The LyX1.1.6fix1 handles the language option by putting it as a global option. Recently, I found this placement make the pdflatex fail with the following message: ! LaTeX Error: Missing \begin{document}. See the LaTeX manual

A bug/fix report for language option in LyX1.1.6fix1

Hi, The LyX1.1.6fix1 handles the language option by putting it as a global option. Recently, I found this placement make the pdflatex fail with the following message: ! LaTeX Error: Missing \begin{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H for immediate

Re: A bug/fix report for language option in LyX1.1.6fix1

Min Xu <[EMAIL PROTECTED]> writes: | Hi, | | The LyX1.1.6fix1 handles the language option by putting it as a global | option. Recently, I found this placement make the pdflatex fail with | the following message: If so, this is a bug in pdflatex or the documentclass or a package file..

Re: A bug/fix report for language option in LyX1.1.6fix1

On Thu, Feb 08, 2001 at 10:05:28AM -0500, Min Xu wrote: > The LyX1.1.6fix1 handles the language option by putting it as a global > option. Recently, I found this placement make the pdflatex fail with the > following message: > > ! LaTeX Error: Missing \begin{document}. >