lyx archive error
I want to export to archive (zip) from export menu. An error popped up. What is that, how can export it in archive file? This is in windows 7, LyX 2.0.2 I can preview pdf and export pdf as usual. regards waluyo <>
how to make sections in bibliography?
Hi, I've tried all day to section my bibliography, but I keep getting errors. The "sectioned bibliography" in document settings is checked. Also two seperate bibtex databases are created, and added these to the bibliography in LyX. When unchecking "sectioned bibliography", the bibliography works fine, but then it is not sectioned. The errors I get are: Missing $ inserted Extra }, or forgotten $ Missing } inserted Do I need to do something else to make sectioned bibliographies work in LyX? Regards, Marco -- I hate it when my foot falls asleep during the day cause that means it's going to be up all night. -- Steven Wright
Re: is lyx really appropriate for my book.
On Feb 15, 2012, at 12:56 PM, Richard Heck wrote:
> On 02/15/2012 11:29 AM, Guenter Milde wrote:
>>> I've also committed to koma-script. I would like to modify the
>>> \@maketitle command. I've located it in scrartcl.cls. Will be studying
>>> it. Will undoubtedly be checking in here later about the changes I've
>>> made, where to put them, and how to use them.
>> The KOMA classes are highly customizable. Please look at the
>> comprehensive documentation in scrguide.pdf (German) or scrguien.pdf
>> (English) for recommended ways to customize the title page(s) before
>> trying the hard way of modifying the maketitle...
>>
> Unfortunately, this particular bit does not appear to be customizable. You
> can change the size of the title font with \setkomafont{title}{...}, but you
> can't do this for authors, and there is no way to affect justification,
> unless it's possible to cancel the \centering command that is issued.
Hmm. I thought koma-script was flexible. -;)
--
Eric Weir
Decatur, GA
eew...@bellsouth.net
"A writer is a person for whom writing is more difficult
than it is for other people."
- Thomas Mann
Re: How to force tex2lyx to read unicode (from within Lyx)?
Jürgen Spitzmüller wrote:
> LuaTeX can use other encodings, but not with non-tex fonts. So if
> \use_non_tex_fonts is true (this is what you want to check for, right?),
> the encoding of the file must be utf8.
No, it is the other way round: If a xetex package is detected,
use_non_tex_fonts is set to true, and the encoding is set to utf8.
> If other encodings are used, LuaTeX uses the "luainputenc" package, which
> has the same syntax than inputenc, i.e.
>
> \usepackage[]{luainputenc}
>
> Maybe we have to care about that.
luainputenc is already handled. What is missing for luatex is to set
use_non_tex_fonts to true and the encoding to utf8 if luainputenc is not
used. Unfortunately this is not so easy as with xetex.
Georg
Re: How to force tex2lyx to read unicode (from within Lyx)?
Jean-Marc Lasgouttes wrote: > Georg, Juergen, I'd like some feedback on the soundness of the patch. I > know next to nil about xetex, and I do not know what is the current > state of the art wrt tex2lyx. Unfortunately I know next to nothing about use_non_tex_fonts. After reading the code and user guide a bit I see that using xetex is only possible if use_non_tex_fonts is true, so your patch looks fine. Georg
Re: Mac-specific: tex2lyx won't run
On Wed, Feb 15, 2012 at 10:59 AM, Eric Weir wrote: > > On Feb 15, 2012, at 10:55 AM, stefano franchi wrote: > >> 3. In Tools>>Preferences>>FIle Converters, create a new converter from >> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and >> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch >> in the "Converter field": >> tex2lyx -e UTF8 -f $$i $$o > > In Tools I do not have the Preferences option. If I go to Preferences > File > Handling > Converters the "add" button is greyed out. I don't see how to add > a new converter. Sorry, that was Linux--As Stephan pointed out, it's in the application menu on the Mac. And, you need to create the new format before you can create the converter. Cheers, Stefano -- __ Stefano Franchi Associate Research Professor Department of Hispanic Studies Ph: +1 (979) 845-2125 Texas A&M University Fax: +1 (979) 845-6421 College Station, Texas, USA stef...@tamu.edu http://stefano.cleinias.org
Re: is lyx really appropriate for my book.
On 02/15/2012 11:29 AM, Guenter Milde wrote:
I've also committed to koma-script. I would like to modify the
\@maketitle command. I've located it in scrartcl.cls. Will be studying
it. Will undoubtedly be checking in here later about the changes I've
made, where to put them, and how to use them.
The KOMA classes are highly customizable. Please look at the
comprehensive documentation in scrguide.pdf (German) or scrguien.pdf
(English) for recommended ways to customize the title page(s) before
trying the hard way of modifying the maketitle...
Unfortunately, this particular bit does not appear to be customizable.
You can change the size of the title font with \setkomafont{title}{...},
but you can't do this for authors, and there is no way to affect
justification, unless it's possible to cancel the \centering command
that is issued.
Richard
Re: Mac-specific: tex2lyx won't run
Am 15.02.2012 um 17:59 schrieb Eric Weir: > > On Feb 15, 2012, at 10:55 AM, stefano franchi wrote: > >> 3. In Tools>>Preferences>>FIle Converters, create a new converter from >> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and >> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch >> in the "Converter field": >> tex2lyx -e UTF8 -f $$i $$o > > In Tools I do not have the Preferences option. If I go to Preferences > File > Handling > Converters the "add" button is greyed out. I don't see how to add > a new converter. Preferences resides in the application menu. LyX -> Preferences... Stephan
Re: is lyx really appropriate for my book.
On Feb 15, 2012, at 11:29 AM, Guenter Milde wrote: > On 2012-02-15, Eric Weir wrote: > >> I've also committed to koma-script. I would like to modify the >> \@maketitle command. I've located it in scrartcl.cls. Will be studying >> it. Will undoubtedly be checking in here later about the changes I've >> made, where to put them, and how to use them. > > The KOMA classes are highly customizable. Please look at the > comprehensive documentation in scrguide.pdf (German) or scrguien.pdf > (English) for recommended ways to customize the title page(s) before > trying the hard way of modifying the maketitle... Thanks, Guenter. I've internalized the advice-- from you previously and others here--to minimize customization of existing classes. I suspect the problem I'm concerned about immediately will be a matter of changing font size specifications for the title and other environments whose defaults are too big for my taste. Probably pretty simple, but it'll probably take some studying on my part. And I do have the koma documentation. Just haven't printed out all 270 pages. Sincerely, -- Eric Weir "Uncertainty is an uncomfortable position, but certainty is an absurd one." - Voltaire
Re: Problem with Change tracking
On 02/14/2012 09:22 PM, Les Denham wrote: I seem to have found an undocumented "feature" of LyX 2.02. If I have Track Changes turned on AND have Show Changes in Output turned on AND have an embedded Gnumeric spreadsheet deleted in the current changes awaiting acceptance or rejection THEN PDFLaTeX dies every time. The solution for me is to make sure I accept the deletion of spreadsheets before I try to make a PDF of the document to sent to my colleagues for them to look at the changes before I accept them. This is how LyX reminds you that you have unaccepted changes. ;-) Can you please file this as a bug? Do you know if it happens only with spreadsheets, or whether it also affects other external insets? Richard
Re: Automated insertion of labeled sentences
On 02/14/2012 05:57 PM, Scott Kostyshak wrote:
From: lyx-users@lists.lyx.org [lyx-users@lists.lyx.org] on behalf of sj03rd
[sjoerd...@gmail.com]
Sent: Tuesday, February 14, 2012 5:15 PM
I can "refer-and-insert" table numbers/equation numbers
using labels and cross-references throughout the text.
Now, it would be extremely valuable if I could also
refer-and-insert a full sentence.
Is this possible in Lyx, and how?
Hi Stewart,
To insert Tex Code, either:
(1) go to Insert> TeX Code
or
(2) type control L
This will give you a red box into which you can type latex commands directly.
Type in something like:
\newcommand{\mysentence}{This is a sentence that I want to use in many places.}
Note that this red box must be before you try to use this command, so put it in
the preamble or near the top of your document.
Then, wherever you want to use that sentence, insert tex code again and put
into the red box:
\mysentence
You should be able to do this in tables and mostly anywhere.
Is this what you were looking for?
Of course, what would really be nice is if LyX allowed "text macros",
like math macros. But this is bug #1704.
Richard
Re: Mac-specific: tex2lyx won't run
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote: > 3. In Tools>>Preferences>>FIle Converters, create a new converter from > Scrivener to Lyx: select "Scrivener" in the From dropdown list, and > "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch > in the "Converter field": > tex2lyx -e UTF8 -f $$i $$o In Tools I do not have the Preferences option. If I go to Preferences > File Handling > Converters the "add" button is greyed out. I don't see how to add a new converter. Thanks, -- Eric Weir "Uncertainty is an uncomfortable position, but certainty is an absurd one." - Voltaire
Re: A couple questions, maybe about koma-script
On Feb 15, 2012, at 11:43 AM, Jürgen Spitzmüller wrote:
> Eric Weir wrote:
> > In formatting a document using koma-script article class, when I apply the
> > bibliography environment LyX inserts "References" followed by this on the
> > line below: "key-1 [1]". What is this? What function does it serve? Not
> > knowing anything it strikes me as irrelevant to my purposes.
>
> This is the label which marks the bibliography item. You'll need it in order
> to refer to an entry. Look at sec 6.5.1 of the User Guide.
>
> > Also, when I compile to pdf I get a single line stranded at the bottom the
> > page. I didn't think this could happen in latex. How do I remedy it?
>
> You can (mostly) avoid such things ("orphans") by changing LaTeX's penalty
> values. I have good experiences with
>
> \tolerance 1414
> \hbadness 1414
> \emergencystretch 1.5em
> \hfuzz 0.3pt
> \widowpenalty = 1
> \vfuzz \hfuzz
> \raggedbottom
>
> However, sometimes orphans and widows are generated anyway (because LaTeX
> thinks it is still the best solution).
Thanks, Jürgen. I'll check out the guide regarding the label. And I'm gonna
hold off on tweaks to eliminate orphans till I'm a little farther along in
getting started with latex/lyx--at least till it becomes more of a problem than
it is on this occasion.
Sincerely,
--
Eric Weir
Clairemont Avenue J3 ~ Decatur, GA 30030
404-636-6142 ~ eew...@bellsouth.net
Re: A couple questions, maybe about koma-script
Eric Weir wrote:
> In formatting a document using koma-script article class, when I apply the
> bibliography environment LyX inserts "References" followed by this on the
> line below: "key-1 [1]". What is this? What function does it serve? Not
> knowing anything it strikes me as irrelevant to my purposes.
This is the label which marks the bibliography item. You'll need it in order
to refer to an entry. Look at sec 6.5.1 of the User Guide.
> Also, when I compile to pdf I get a single line stranded at the bottom the
> page. I didn't think this could happen in latex. How do I remedy it?
You can (mostly) avoid such things ("orphans") by changing LaTeX's penalty
values. I have good experiences with
\tolerance 1414
\hbadness 1414
\emergencystretch 1.5em
\hfuzz 0.3pt
\widowpenalty = 1
\vfuzz \hfuzz
\raggedbottom
However, sometimes orphans and widows are generated anyway (because LaTeX
thinks it is still the best solution).
Jürgen
Re: is lyx really appropriate for my book.
On 2012-02-15, Eric Weir wrote: > On Feb 14, 2012, at 3:27 AM, Richard Heck wrote: >> On 02/14/2012 07:01 AM, Eric Weir wrote: >>> On Feb 13, 2012, at 6:34 PM, Steve Litt wrote: >> You just put them in as author and title, and fix the typography >> later. One easy way to do it is just to copy the code that sets the >> title from the document class, in this case scrartcl.cls, and modify >> it as you see fit. Depending upon whether you have a title page or >> not, this is either the \maketitle command or else the \@maketitle >> command. > I don't understand, Richard. This sounds like the normal procedure and > what I've been doing and not liking the result. I took Steve to be > suggesting going around that. Would not be surprised if I didn't > understand. > I've also committed to koma-script. I would like to modify the > \@maketitle command. I've located it in scrartcl.cls. Will be studying > it. Will undoubtedly be checking in here later about the changes I've > made, where to put them, and how to use them. The KOMA classes are highly customizable. Please look at the comprehensive documentation in scrguide.pdf (German) or scrguien.pdf (English) for recommended ways to customize the title page(s) before trying the hard way of modifying the maketitle... Günter
Re: How to force tex2lyx to read unicode (from within Lyx)?
On 2012-02-15, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> I thought LuaTeX could use encdings other than utf8. Is utf8 the
>> default? And does it use the same packages as XeTeX?
> LuaTeX can use other encodings, but not with non-tex fonts.
Are you sure. I'd think that with "luainputenc" there would be no limitation
of the input encoding to utf8. Of course, with non-tex fonts the *font
encoding* is Unicode.
> So if
> \use_non_tex_fonts is true (this is what you want to check for,
> right?), the encoding of the file must be utf8.
This might be a LyX limitation. However this is about tex2lyx, so we would
check for \usepackage{fontenc} or \usepackage{xunicode}.
I propose to also check for
> \usepackage[]{luainputenc}
Günter
Re: Mac-specific: tex2lyx won't run
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote: > following on Enrico's excellent suggestion, here is how you can solve > your Scrivener-related problem in a Lyx-way. The developers are > working on a permanent solution, it seems. So this may turn > unnecessary very shortly. At any rate, here it goes: > > 1, Create a new format in Tools>>Preferences>>File formats. Click > "New" and call it Scrivener or something like it. > > 2. Save. > > 3. In Tools>>Preferences>>FIle Converters, create a new converter from > Scrivener to Lyx: select "Scrivener" in the From dropdown list, and > "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch > in the "Converter field": > tex2lyx -e UTF8 -f $$i $$o > > 4. Click "Add" and click "Save." > > Now you should have the "Scrivener" (or whatever you called the > format) option in File>>Import, without needing to go to the command > line. In fact Lyx does internally exactaly what you'd on the command > line. Thanks, Stefano. I was hoping after hearing from Enrico that something like that might be possible. Sincerely, -- Eric Weir Decatur, GA USA eew...@bellsouth.net "Imagining the other is a powerful antidote to fanaticism and hatred." - Amos Oz
Re: is lyx really appropriate for my book.
2012/2/15 Marcelo Acuña : > > For title page I decided to do them with ERT for spacing and alignment, and > all the material in a separate file which then included. You can also do > with a graphic design application, create a file and then include it. > Marcelo > The textpos latex package (http://www.ctan.org/pkg/textpos) allows precise positioning of blocks of text on a page, with input in mm (or pt). It's one way to typeset a title page (or title pages, for a book) with ERT. That's what I eventually used for my book. Cheers, Stefano -- __ Stefano Franchi Associate Research Professor Department of Hispanic Studies Ph: +1 (979) 845-2125 Texas A&M University Fax: +1 (979) 845-6421 College Station, Texas, USA stef...@tamu.edu http://stefano.cleinias.org
Re: is lyx really appropriate for my book.
On Feb 15, 2012, at 10:04 AM, Marcelo Acuña wrote: > >>> In your book's main matter, use styles and nothing but styles. Never > >>> apply an appearance directly, but instead apply appearances through > >>> styles that match the usage in the document (Chapter, section, > >>> subsection, Quote, tip, warning, etc). BUT, in the front matter, feel > >>> free to apply appearances directly, and DO NOT use the document class's > >>> facilities for title, author, etc, and just write them with proper > >>> appearances and spacing. > >> > >> Am I correct in understand you that I can just skip using the title and > >> author environments and write and format the as if body text? Recently I > >> tried formatting a title using the section environment and it would not > >> compile to pdf without the title and author data. > > > > You just put them in as author and title, and fix the typography later. One > > easy way to do it is just to copy the code that sets the title from the > > document class, in this case scrartcl.cls, and modify it as you see fit. > > Depending upon whether you have a title page or not, this is either the > > \maketitle command or else the \@maketitle command. > > I don't understand, Richard. This sounds like the normal procedure and what > I've been doing and not liking the result. I took Steve to be suggesting > going around that. Would not be surprised if I didn't understand. > > Eric > -- > > For title page I decided to do them with ERT for spacing and alignment, and > all the material in a separate file which then included. You can also do with > a graphic design application, create a file and then include it. Thanks, Marcelo. My document is an article, so I don't have a title page. My beef with what koma-script does with the title and author is the size of the font. Way, way too big for my taste. Might also want to have them left-justified instead of centered, but that is less important. Sincerely, -- Eric Weir Decatur, GA USA eew...@bellsouth.net "Hatred destroys. Love heals." - Eknath Easwaran
Re: Mac-specific: tex2lyx won't run
On Wed, Feb 15, 2012 at 5:45 AM, Eric Weir wrote: > > On Feb 14, 2012, at 4:47 PM, Enrico Forestieri wrote: > >> Eric Weir writes: >>> I'm attempting to use the workaround suggested by Stefano to get LyX to >>> recognize a Unicoded document as Unicoded. The workaround involves use >>> of the tex2lyx command. >>> >>> I'm on a Mac. When I run the command I get a command not found message. >>> When I do locate tex2lyx, however, the file shows up in two locations: >>> /Applications/LyX.app/Contents/MacOS and >>> /Applications/TeX/LyX.app/Contents/MacOS >>> >>> How do I get the command to run? >> >> Why don't you simply modify the converter in >> Tools->Preferences->File Handling->Converters->LaTeX (plain) -> LyX >> and then use File->Import->LaTeX (plain) ? > > Thanks, Enrico. I've checked that out. With help it may be something I'd want > to try. For now, I got the command to run by specifying the path and with the > default settings in document > settings compiling to pdflatex recognizes the > unicode coding. > Eric, following on Enrico's excellent suggestion, here is how you can solve your Scrivener-related problem in a Lyx-way. The developers are working on a permanent solution, it seems. So this may turn unnecessary very shortly. At any rate, here it goes: 1, Create a new format in Tools>>Preferences>>File formats. Click "New" and call it Scrivener or something like it. 2. Save. 3. In Tools>>Preferences>>FIle Converters, create a new converter from Scrivener to Lyx: select "Scrivener" in the From dropdown list, and "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch in the "Converter field": tex2lyx -e UTF8 -f $$i $$o 4. Click "Add" and click "Save." Now you should have the "Scrivener" (or whatever you called the format) option in File>>Import, without needing to go to the command line. In fact Lyx does internally exactaly what you'd on the command line. Cheers, Stefano -- __ Stefano Franchi Associate Research Professor Department of Hispanic Studies Ph: +1 (979) 845-2125 Texas A&M University Fax: +1 (979) 845-6421 College Station, Texas, USA stef...@tamu.edu http://stefano.cleinias.org
A couple questions, maybe about koma-script
In formatting a document using koma-script article class, when I apply the bibliography environment LyX inserts "References" followed by this on the line below: "key-1 [1]". What is this? What function does it serve? Not knowing anything it strikes me as irrelevant to my purposes. Also, when I compile to pdf I get a single line stranded at the bottom the page. I didn't think this could happen in latex. How do I remedy it? Thanks, -- Eric Weir Decatur, GA eew...@bellsouth.net "A man should be in the world as though he were not in it so that it will be no worse because of his life." - Wendell Berry
Re: is lyx really appropriate for my book.
>>> In your book's main matter, use styles and nothing but styles. Never >>> apply an appearance directly, but instead apply appearances through >>> styles that match the usage in the document (Chapter, section, >>> subsection, Quote, tip, warning, etc). BUT, in the front matter, feel >>> free to apply appearances directly, and DO NOT use the document class's >>> facilities for title, author, etc, and just write them with proper >>> appearances and spacing. >> >> Am I correct in understand you that I can just skip using the title and >> author environments and write and format the as if body text? Recently I >> tried formatting a title using the section environment and it would not >> compile to pdf without the title and author data. > > You just put them in as author and title, and fix the typography later. One > easy way to do it is just to copy the code that sets the title from the > document class, in this case scrartcl.cls, and modify it as you see fit. > Depending upon whether you have a title page or not, this is either the > \maketitle command or else the \@maketitle command. I don't understand, Richard. This sounds like the normal procedure and what I've been doing and not liking the result. I took Steve to be suggesting going around that. Would not be surprised if I didn't understand. Eric -- For title page I decided to do them with ERT for spacing and alignment, and all the material in a separate file which then included. You can also do with a graphic design application, create a file and then include it. Marcelo
Re: Mac-specific: tex2lyx won't run
On Feb 14, 2012, at 4:47 PM, Enrico Forestieri wrote: > Eric Weir writes: >> I'm attempting to use the workaround suggested by Stefano to get LyX to >> recognize a Unicoded document as Unicoded. The workaround involves use >> of the tex2lyx command. >> >> I'm on a Mac. When I run the command I get a command not found message. >> When I do locate tex2lyx, however, the file shows up in two locations: >> /Applications/LyX.app/Contents/MacOS and >> /Applications/TeX/LyX.app/Contents/MacOS >> >> How do I get the command to run? > > Why don't you simply modify the converter in > Tools->Preferences->File Handling->Converters->LaTeX (plain) -> LyX > and then use File->Import->LaTeX (plain) ? Thanks, Enrico. I've checked that out. With help it may be something I'd want to try. For now, I got the command to run by specifying the path and with the default settings in document > settings compiling to pdflatex recognizes the unicode coding. It's a workaround. I hope there will eventually be a fix to the problem that will make it unnecessary. If not the solution you suggest may work--again, with help. Sincerely, -- Eric Weir Decatur, GA eew...@bellsouth.net "Style is truth." - Ray Bradbury
Re: is lyx really appropriate for my book.
On Feb 14, 2012, at 3:27 AM, Richard Heck wrote: > On 02/14/2012 07:01 AM, Eric Weir wrote: > >> On Feb 13, 2012, at 6:34 PM, Steve Litt wrote: >> >>> In your book's main matter, use styles and nothing but styles. Never >>> apply an appearance directly, but instead apply appearances through >>> styles that match the usage in the document (Chapter, section, >>> subsection, Quote, tip, warning, etc). BUT, in the front matter, feel >>> free to apply appearances directly, and DO NOT use the document class's >>> facilities for title, author, etc, and just write them with proper >>> appearances and spacing. >> >> Am I correct in understand you that I can just skip using the title and >> author environments and write and format the as if body text? Recently I >> tried formatting a title using the section environment and it would not >> compile to pdf without the title and author data. > > You just put them in as author and title, and fix the typography later. One > easy way to do it is just to copy the code that sets the title from the > document class, in this case scrartcl.cls, and modify it as you see fit. > Depending upon whether you have a title page or not, this is either the > \maketitle command or else the \@maketitle command. I don't understand, Richard. This sounds like the normal procedure and what I've been doing and not liking the result. I took Steve to be suggesting going around that. Would not be surprised if I didn't understand. I've also committed to koma-script. I would like to modify the \@maketitle command. I've located it in scrartcl.cls. Will be studying it. Will undoubtedly be checking in here later about the changes I've made, where to put them, and how to use them. Thanks, -- Eric Weir Decatur, GA eew...@bellsouth.net "What is man without the beasts? If all the beasts were gone, men would die from a great loneliness of spirit." - Chief Seattle
Re: How to force tex2lyx to read unicode (from within Lyx)?
Jean-Marc Lasgouttes wrote:
> I thought LuaTeX could use encdings other than utf8. Is utf8 the
> default? And does it use the same packages as XeTeX?
LuaTeX can use other encodings, but not with non-tex fonts. So if
\use_non_tex_fonts is true (this is what you want to check for, right?), the
encoding of the file must be utf8.
If other encodings are used, LuaTeX uses the "luainputenc" package, which has
the same syntax than inputenc, i.e.
\usepackage[]{luainputenc}
Maybe we have to care about that.
The font packages are the same (basically fontspec).
Jürgen
Re: How to force tex2lyx to read unicode (from within Lyx)?
Le 15/02/2012 11:38, Jürgen Spitzmüller a écrit : Jean-Marc Lasgouttes wrote: > I have a patch that seems to work with XeTeX, I do not know anything > about luatex (what shall we do with it?) I think your patch will work for LuaTeX as well. I thought LuaTeX could use encdings other than utf8. Is utf8 the default? And does it use the same packages as XeTeX? I am very confused by these different engines... JMarc
Re: How to force tex2lyx to read unicode (from within Lyx)?
Jean-Marc Lasgouttes wrote: > I have a patch that seems to work with XeTeX, I do not know anything > about luatex (what shall we do with it?) I think your patch will work for LuaTeX as well. Jürgen
Re: How to force tex2lyx to read unicode (from within Lyx)?
Le 15/02/2012 10:51, Guenter Milde a écrit : IMV, it should try utf8 first in case this does not give a result. * if the file is pure ASCII, everything is fine * if the file is utf8 encoded, fine too * if another encoding is used, an error occures: try again with the second guess. That is not a bad solution, but probably not so easy to implement with our current code. I have a patch that seems to work with XeTeX, I do not know anything about luatex (what shall we do with it?) JMarc
Re: Roman numbering in bibliography
Emil Pavlov wrote:
> Sorry, but this doesn't work for me. I am sending you my lyx and the bib
> files.
What does not work? The pagination is switched to Roman as requested. You mean
that the roman pagination starts too early? Try
\setbibpreamble{%
\pagenumbering{Roman}
\setcounter{page}{1}
}
instead.
HTH
Jürgen
Re: Roman numbering in bibliography
?? 14.02.2012 13:01, Jürgen Spitzmüller ??:
Emil Pavlov wrote:
> I have inserted an external bibtex bibliography in my lyx document and I
> would like to change the numbering in the bibliography section to
> capital roman numbers. The problem is that my document class is report
> (KOMA), so the command \backmatter isn't available.
\pagenumbering{Roman}
\setcounter{page}{1}
Jürgen
Sorry, but this doesn't work for me. I am sending you my lyx and the bib
files.
Emil
% This file was created with JabRef 2.7b.
% Encoding: UTF-8
@ARTICLE{Adam2011,
author = {Adam, T. and others},
title = {Measurement of the neutrino velocity with the OPERA detector in the
CNGS beam},
journal = {eprint arXiv:1109.4897},
year = {2011},
archiveprefix = {arXiv},
collaboration = {OPERA Collaboration},
eprint = {1109.4897},
owner = {emil},
primaryclass = {hep-ex},
slaccitation = {%%CITATION = ARXIV:1109.4897;%%},
timestamp = {2012.02.09}
}
@ARTICLE{Ahmad2001,
author = {Ahmad, Q. R. and others},
title = {Measurement of the Rate of $\upnu_mathrm{e}+\mathrm{d} \rightarrow
\mathrm{p}+\mathrm{p}+{\mathrm{e}}^{-}$ Interactions Produced by
$^{8}\mathrm{B}$ Solar Neutrinos at the Sudbury Neutrino Observatory},
journal = {Phys. Rev. Lett.},
year = {2001},
volume = {87},
pages = {071301},
month = {Jul},
collaboration = {(SNO Collaboration)},
doi = {10.1103/PhysRevLett.87.071301},
issue = {7},
numpages = {6},
owner = {emil},
publisher = {American Physical Society},
timestamp = {2012.02.08},
url = {http://link.aps.org/doi/10.1103/PhysRevLett.87.071301}
}
@ARTICLE{Angrik2005,
author = {Angrik, J. and Armbrust, T. and Beglarian, A. and Besserer, U. and
Blumer, J. and others},
title = {KATRIN design report 2004. KATRIN design report 2004.},
year = {2005},
__markedentry = {[emil:]},
owner = {emil},
timestamp = {2012.02.10}
}
@ARTICLE{Auger1923,
author = {Pierre Victor Auger},
title = {Sur les rayons $\beta$ secondaires produits dans un gaz par des rayons
X},
journal = {Comptes rendus hebdomadaires des séances de l'Académie des sciences
/ publiés...},
year = {1923},
pages = {169-171},
owner = {emil},
timestamp = {2012.01.16},
url = {http://gallica.bnf.fr/ark:/12148/bpt6k3130n.image.f187.langFR#}
}
@ARTICLE{Bambynek1977,
author = {Bambynek, W. and Behrens, H. and Chen, M. H. and Crasemann, B. and
Fitzpatrick, M. L. and Ledingham, K. W. D. and Genz, H. and Mutterer,
M. and Intemann, R. L.},
title = {Orbital electron capture by the nucleus},
journal = {Rev. Mod. Phys.},
year = {1977},
volume = {49},
pages = {77--221},
month = {Jan},
doi = {10.1103/RevModPhys.49.77},
file = {:/home/emil/STUDIUM HD/Bachelorarbeit/Decays/bambynek ec.pdf:PDF},
issue = {1},
owner = {emil},
publisher = {American Physical Society},
timestamp = {2011.11.28},
url = {http://link.aps.org/doi/10.1103/RevModPhys.49.77}
}
@ARTICLE{Bearden1967,
author = {Bearden, J. A. and Burr, A. F.},
title = {Reevaluation of X-Ray Atomic Energy Levels},
journal = {Rev. Mod. Phys.},
year = {1967},
volume = {39},
pages = {125--142},
month = {Jan},
doi = {10.1103/RevModPhys.39.125},
file = {:/home/emil/STUDIUM HD/Bachelorarbeit/Articles/energy levels reevaluated ref:PDF},
issue = {1},
owner = {emil},
publisher = {American Physical Society},
timestamp = {2012.01.24},
url = {http://link.aps.org/doi/10.1103/RevModPhys.39.125}
}
@BOOKLET{Berger2012,
title = {XCOM: Photon Cross Section Database (version 1.5)},
author = {Berger, M.J. and Hubbell, J.H. and Seltzer, S.M. and Chang, J. and
Coursey, J.S. and Sukumar, R. and Zucker, D.S. and Olsen, K.},
howpublished = {Online},
lastchecked = {[Thursday, 26-Jan-2012 06:52:31 EST]},
address = {http://physics.nist.gov/xcom},
year = {2012},
note = {National Institute of Standards and Technology, Gaithersburg, MD},
owner = {emil},
timestamp = {2012.01.26},
url = {http://physics.nist.gov/xcom}
}
@ARTICLE{Beyer1983,
author = {G.J. Beyer and A. De Rújula and R.-D. Von Dincklage and H.Ã
. Gustafsson
and P.G. Hansen and P. Hoff and B. Jonson and H.L. Ravn and K. Riisager},
title = {The q-value of 157Tb},
journal = {Nuclear Physics A},
year = {1983},
volume = {408},
pages = {87 - 98},
number = {1},
abstract = {Using mass-separated and chemically purified samples, the Q-value
of 157Tb has been remeasured as 62.9 ± 0.7 keV by determining electron
capture ratios. The transition probability to the excited state was
found to be (1.1 ± 0.1) à 10â3, with a transition energy of 8.4 ±
0.7 keV for this branch. From the proximity to the 2s binding energy,
experiments on the internal bremsstrahlung electron capture seem
feasible. The half-life of 157Tb was remeasured as 99 ± 10 y.},
doi = {10.1016/0375-9474(83)90350-0},
issn = {0375-9474},
keywords = {Radioactivity},
owner = {emil},
timestamp = {2012.01.24},
url = {http://www.sciencedirect.com/science/art
Re: How to force tex2lyx to read unicode (from within Lyx)?
On 2012-02-14, stefano franchi wrote:
> On Tue, Feb 14, 2012 at 8:05 AM, Jean-Marc Lasgouttes
>> tex2lyx is not really the culprit. The file you attach is broken : it
>> does not use xetex/luatex, but it does use "Unicode (XeTeX) (utf8)" as
>> encoding. As a result, the latex export of the file does not specify
>> any encoding, and tex2lyx is not able to guess it.
> Sorry, but I don't understand what you mean by "broken" here. If I set
> the encoding to pure Unicode (isn't that what "Unicode (XeTeX) (utf8)"
> means?) shouldn't that be enough to specify that the file is
> Unicode-encoded?
The setting "Unicode (XeTeX) (utf8)" specifies that the LyX-generated LaTeX
file should be utf-8 encoded Unicode
* without "forced" substitutions (for characters the halfway utf8 support
of 8-bit LaTeX does not understand or does wrong), and
* without calling the "inputenc" package.
This means that in the exported file, utf-8 encoding is used but there is no
specification of the used encoding inside the *.tex file.
You can consider this an "expert setting": it allows to circumvent
limitations but usually requires additional custom preamble code to
produce valid LaTeX files.
Similar to the use of ERT, LyX does not guarantee proper working.
> That seems obvious to me (which of course may only reflect my ignorance
> of Lyx code). If that's not true then I do not understand what is the
> meaning of the Document>>Settings>Language>>Encoding value.
It seems that tex2lyx relies on the optional argument in the
\usepackage[]{inputenc}
line to determine the *.tex file encoding.
IMV, it should try utf8 first in case this does not give a result.
* if the file is pure ASCII, everything is fine
* if the file is utf8 encoded, fine too
* if another encoding is used, an error occures: try again with the second
guess.
Günter
