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

2013-05-25 Thread Jürgen Spitzmüller
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)

2013-05-25 Thread Scott Kostyshak
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 encoding latin1 whereas before it
 had encoding utf-8.

 Try again.

Works well, thanks.

Scott


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

2013-05-25 Thread Jürgen Spitzmüller
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)

2013-05-25 Thread Scott Kostyshak
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 file has encoding latin1 whereas before it
>> had encoding utf-8.
>
> Try again.

Works well, thanks.

Scott


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

2013-05-23 Thread Scott Kostyshak
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 trunk)
 is pasted below. After adding the English class option and adding
 babel to the preamble, the export works fine. Is this what should be
 done to the document or is it an internal issue?

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.

Scott


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

2013-05-23 Thread Scott Kostyshak
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 current trunk)
>> is pasted below. After adding the English class option and adding
>> babel to the preamble, the export works fine. Is this what should be
>> done to the document or is it an internal issue?

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.

Scott


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

2013-05-20 Thread Jürgen Spitzmüller
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
 babel to the preamble, the export works fine. Is this what should be
 done to the document or is it an internal issue?

Thanks, fixed.

Jürgen


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

2013-05-20 Thread Jürgen Spitzmüller
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
> babel to the preamble, the export works fine. Is this what should be
> done to the document or is it an internal issue?

Thanks, fixed.

Jürgen


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

2013-05-19 Thread Scott Kostyshak
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 export works fine. Is this what should be
done to the document or is it an internal issue?

Scott

commit 566a5f2b7513ffbd75cc92f713dc2636f37e
Author: Juergen Spitzmueller sp...@lyx.org
Date:   Mon Jul 23 11:36:55 2012 +0200

Fixes to the language package call

* Assure that really no language package is called when none is selected.
* Only call global custom package if global is desired.
This is a candidate for branch as well.

[diff from before and after when exporting to LaTeX (pdflatex)]

-\documentclass[12pt,a4paper,english,cjk]{book}
+\documentclass[12pt,a4paper,cjk]{book}
 \usepackage[T1]{fontenc}
 \usepackage{CJKutf8}
 \setcounter{secnumdepth}{3}
 \setcounter{tocdepth}{3}
 \usepackage{color}
-\usepackage{babel}
 \usepackage{pmboxdraw}
 \usepackage{graphicx}
 \usepackage{setspace}


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

2013-05-19 Thread Scott Kostyshak
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 export works fine. Is this what should be
done to the document or is it an internal issue?

Scott

commit 566a5f2b7513ffbd75cc92f713dc2636f37e
Author: Juergen Spitzmueller 
Date:   Mon Jul 23 11:36:55 2012 +0200

Fixes to the language package call

* Assure that really no language package is called when none is selected.
* Only call global custom package if global is desired.
This is a candidate for branch as well.

[diff from before and after when exporting to LaTeX (pdflatex)]

-\documentclass[12pt,a4paper,english,cjk]{book}
+\documentclass[12pt,a4paper,cjk]{book}
 \usepackage[T1]{fontenc}
 \usepackage{CJKutf8}
 \setcounter{secnumdepth}{3}
 \setcounter{tocdepth}{3}
 \usepackage{color}
-\usepackage{babel}
 \usepackage{pmboxdraw}
 \usepackage{graphicx}
 \usepackage{setspace}


Re: Language option

2001-02-17 Thread Dekel Tsur

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 preferences dialog,
   and if this button is selected, babel will not be used for all documents
   whose language is equal to default_language.
  
  the second one is a good idea!
 
 Actually, we can have a 3 choice button:
  - Do not use babel
  - Use babel, the language is given as an argument to the babel package
  - Use babel, the language is given as an argument to \documentclass

I've decided to use two boolean buttons.
I've attached a patch. Any comments before I apply it?


 patch.gz


Re: Language option

2001-02-17 Thread Dekel Tsur

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 preferences dialog,
> > > and if this button is selected, babel will not be used for all documents
> > > whose language is equal to default_language.
> > 
> > the second one is a good idea!
> 
> Actually, we can have a 3 choice button:
>  - Do not use babel
>  - Use babel, the language is given as an argument to the babel package
>  - Use babel, the language is given as an argument to \documentclass

I've decided to use two boolean buttons.
I've attached a patch. Any comments before I apply it?


 patch.gz


Language option

2001-02-13 Thread Herbert Voss

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 PROTECTED]
http://perce.de/lyx/





RE: Language option

2001-02-13 Thread Juergen Vigna


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 heavily, so I don't think
we'll add this again.

  Jrgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jrgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

You will live to see your grandchildren.




Re: Language option

2001-02-13 Thread Dekel Tsur

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 not be used for all documents
  whose language is equal to default_language.
 
 the second one is a good idea!

Actually, we can have a 3 choice button:
 - Do not use babel
 - Use babel, the language is given as an argument to the babel package
 - Use babel, the language is given as an argument to \documentclass



Language option

2001-02-13 Thread Herbert Voss

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 PROTECTED]
http://perce.de/lyx/





RE: Language option

2001-02-13 Thread Juergen Vigna


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 heavily, so I don't think
we'll add this again.

  Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

You will live to see your grandchildren.




Re: Language option

2001-02-13 Thread Dekel Tsur

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 not be used for all documents
> > whose language is equal to default_language.
> 
> the second one is a good idea!

Actually, we can have a 3 choice button:
 - Do not use babel
 - Use babel, the language is given as an argument to the babel package
 - Use babel, the language is given as an argument to \documentclass



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

2001-02-09 Thread Min Xu

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 language option is specified at the place 
where it is used, i.e., by:
\usepackage[language]{babel}

Min



  ! LaTeX Error: Missing \begin{document}.
  
  See the LaTeX manual or LaTeX Companion for explanation.
  Type  H return  for immediate help.
  ... 
  
  l.1478 \ProcessOptionsWithKV{Hyp}
 
 I think that the problem here is the hyperref package.
 Try installing the latest version of hyperref from CTAN.



 PGP signature


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

2001-02-09 Thread Dekel Tsur

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 language option is 
 used.

Report this bug to the author(s) of prosper (and the other packages).

 Does it make more sense that the language option is specified at the place 
 where it is used, i.e., by:
 \usepackage[language]{babel}

No, because there are other packages that use the language option.



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

2001-02-09 Thread Lars Gullik Bjønnes

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

Then this is a bug in prosper. File a bug report please.

| Does it make more sense that the language option is specified at the place 
| where it is used, i.e., by:
| \usepackage[language]{babel}

It is not only babel that use the language string, and that is the
pooint in setting in the documentclass option: all packages that can
be laguage tunable can then take advantage of it.

Lgb



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

2001-02-09 Thread Min Xu

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 language option is specified at the place 
where it is used, i.e., by:
\usepackage[language]{babel}

Min



> > ! LaTeX Error: Missing \begin{document}.
> > 
> > See the LaTeX manual or LaTeX Companion for explanation.
> > Type  H   for immediate help.
> > ... 
> > 
> > l.1478 \ProcessOptionsWithKV{Hyp}
> 
> I think that the problem here is the hyperref package.
> Try installing the latest version of hyperref from CTAN.



 PGP signature


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

2001-02-09 Thread Dekel Tsur

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 language option is 
> used.

Report this bug to the author(s) of prosper (and the other packages).

> Does it make more sense that the language option is specified at the place 
> where it is used, i.e., by:
> \usepackage[language]{babel}

No, because there are other packages that use the language option.



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

2001-02-09 Thread Lars Gullik Bjønnes

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

Then this is a bug in prosper. File a bug report please.

| Does it make more sense that the language option is specified at the place 
| where it is used, i.e., by:
| \usepackage[language]{babel}

It is not only babel that use the language string, and that is the
pooint in setting in the documentclass option: all packages that can
be laguage tunable can then take advantage of it.

Lgb



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

2001-02-08 Thread Min Xu

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  for immediate help.
... 

l.1478 \ProcessOptionsWithKV{Hyp}


While after removing the language global option and replace the babel 
line by:
\usepackage[american]{babel}
fixed the problem.

This bug appears in a foils lyx file which can be found at Oscar's web 
site. http://www.iit.upco.es/~oscar/download/Presentation.tgz

Please cc to [EMAIL PROTECTED] as I am not subscribed to this 
mailing list.

Min Xu




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

2001-02-08 Thread Lars Gullik Bjønnes

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 send a test document that shows this behaviour?

Lgb



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

2001-02-08 Thread Dekel Tsur

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 or LaTeX Companion for explanation.
 Type  H return  for immediate help.
 ... 
 
 l.1478 \ProcessOptionsWithKV{Hyp}

I think that the problem here is the hyperref package.
Try installing the latest version of hyperref from CTAN.



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

2001-02-08 Thread Min Xu

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

l.1478 \ProcessOptionsWithKV{Hyp}


While after removing the language global option and replace the babel 
line by:
\usepackage[american]{babel}
fixed the problem.

This bug appears in a foils lyx file which can be found at Oscar's web 
site. http://www.iit.upco.es/~oscar/download/Presentation.tgz

Please cc to [EMAIL PROTECTED] as I am not subscribed to this 
mailing list.

Min Xu




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

2001-02-08 Thread Lars Gullik Bjønnes

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 send a test document that shows this behaviour?

Lgb



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

2001-02-08 Thread Dekel Tsur

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 or LaTeX Companion for explanation.
> Type  H   for immediate help.
> ... 
> 
> l.1478 \ProcessOptionsWithKV{Hyp}

I think that the problem here is the hyperref package.
Try installing the latest version of hyperref from CTAN.