Re: need help with numeration in lyx
Dave, I do not quite understand your issue. What are the "1. blablabla" "2. blublublu" etc? Sections? Items in a list? Perhaps you could send along a minimal example. It'd be easier to help you. Stefano On Thu, Dec 2, 2010 at 4:13 PM, davy wrote: > hello, > > I am a German mother tongue speaker and hope you can understand my English. > > I have a document the following way... > > Chapter 1 blablabla > > 1 blablabla > 2 blublublu > > Chapter 2 ljljljljljl > > 3 blobloblo > 4 bliblibli > 5 blebleble > > I need it though like this... > > Chapter 1 blablabla > > 1 blablabla > 2 blublublu > > Chapter 2 ljljljljljl > > 1 blobloblo > 2 bliblibli > 3 blebleble > > can I do this in Lyx? > > Thanks a lot > > Davy > >
need help with numeration in lyx
hello, I am a German mother tongue speaker and hope you can understand my English. I have a document the following way... Chapter 1 blablabla 1 blablabla 2 blublublu Chapter 2 ljljljljljl 3 blobloblo 4 bliblibli 5 blebleble I need it though like this... Chapter 1 blablabla 1 blablabla 2 blublublu Chapter 2 ljljljljljl 1 blobloblo 2 bliblibli 3 blebleble can I do this in Lyx? Thanks a lot Davy
Re: How can I restart enumeration of a episode after a chapter
hello, I am a German mother tongue speaker and hope you can understand my English. I have a document the following way... Chapter 1 blablabla 1 blablabla 2 blublublu Chapter 2 ljljljljljl 3 blobloblo 4 bliblibli 5 blebleble I need it though like this... Chapter 1 blablabla 1 blablabla 2 blublublu Chapter 2 ljljljljljl 1 blobloblo 2 bliblibli 3 blebleble can I do this in Lyx? Thanks a lot Davy
Re: LyX and Lithuanian language
I can verify the problem and found the reason: in the latest version if the lithuanian package one needs to use the font encoding "L7x". and une _must_not_ use the encoding ISO 8859-13 but uft8x. L7x is a very non-standard font encoding: The font choice will be limited to Latin Modern and the PSNFSS fonts. But it work here fior me will all installed fonts (maybe they are all PSNFSS fonts). utf8x loads the unsupported, non-standard ucs package that can lead to clashes with other packages. OK, but to be able to write Lithuanian it seems one has to live with that limitations. In the attached file I used this encoding. To change the font encoding, you must open LyX's preverences and replace "T1" with "L7x" in the field "TeX encoding" that you find under Output->LaTeX. Better, replace "T1" with "L7x,T1", so that T1 is still the default encoding (for English and other languages that do not change the font-encoding) and L7x is available for Lithuanian. We could add preamble code to load the file "l7xenc.def" if it exists to the "languages" file: \IfFileExists{l7xenc.def}{\input{l7xenc.def}{} This would declare L7x whenever Lithuanian is used in the document. Thanks for these infos. Can you please update the Lithuanian page in the Wiki accordingly? If yes, I'll make utf8x the default encoding for Lithuanian for the next LyX release. Please don't if it can be avoided. I suggest "ASCII" instead: LyX will handle the Unicode->TeX conversion then (and it does a good job at this). I don't understand. ASCII is a 7bit encoding utf8x an 8bit encoding. how does LyX convert the encoding? thanks and regards Uwe
Re: limit in number of reference entries in *.bib coming from jabref and used in lyx ? entries in reference list are cut off
Birte Schoettker gmail.com> writes: Rainer: I would love to know that, too, how to identify non-ASCII characters in a bibtex file. On Linux (or probably most POSIX-compatible systems), you have the iconv command. So iconv -t ASCII myfile.bib | grep iconv will try to convert your .bib file to ASCII and, if it fails, print the error message iconv generated (which includes the position of the offending character). The position is a character count, not a line/column pair, so it might be easier to go with iconv -t ASCII myfile.bib (which writes the converted file to the display) and see where in the file iconv died. There are ports of iconv to Windows as well (I use the MinGW port at home). /Paul
Re: LyZ: lyxpipe changes in 2.0?
Jose Quesada wrote: > /home/user/.lyx/lyxpipe.in > /home/user/.lyx/lyxpipe.out > > I never cared to look for this before because it worked, it may have always > been like that... yes, just try to run 1.6 and you will find them there. pavel
Re: limit in number of reference entries in *.bib coming from jabref and used in lyx ? entries in reference list are cut off
> > 2. I found a 'dodgy' reference in my list at "Wa..." (alphabetical order). > After that was removed, everything worked fine:). I have ended up doing this - usually more than once until all problem characters are removed. > > @ Uwe: I thank you very much for your relevant comment; and you are right. > My list has resulted from the merger of a five year, multi-disciplinary > project. So, yes, I won't need all of them and should have 'cleaned out > earlier' for the sake of overview at least. And I do my best not to torture > the reviewer with inadequate referencing, though I might have been quite > thorough. I also tend to use an enormous bibtex file primarily for managing my references, and secondarily for inserting into documents. > > @ Rainer: I would love to know that, too, how to identify non-ASCII > characters in a bibtex file. > The main culprits I have found are 'smart-quotes' and n-and m-dashes. Some non-english accents are easier to spot, and occasionally symbols can cause problems too. The problem characters are often in abstracts or review fields. Jabref works quite happily for looking references up though even with all the illegal characters. -- Stephen
Re: limit in number of reference entries in *.bib coming from jabref and used in lyx ? entries in reference list are cut off
Hi all, thank you very much for your quick and useful responses. 1. To cut the file in two did not make a difference. 2. I found a 'dodgy' reference in my list at "Wa..." (alphabetical order). After that was removed, everything worked fine:). @ Richard: Great hints. It must have been an illegal character, which I could not immediately identify when looking at that reference and it was not the first one that didn't appear. I will next time rather launch LyX from a terminal and I will try ASCII encoding, but have to see how I go with my special characters. Thank you for the kind offer of help. @ Uwe: I thank you very much for your relevant comment; and you are right. My list has resulted from the merger of a five year, multi-disciplinary project. So, yes, I won't need all of them and should have 'cleaned out earlier' for the sake of overview at least. And I do my best not to torture the reviewer with inadequate referencing, though I might have been quite thorough. @ Rainer: I would love to know that, too, how to identify non-ASCII characters in a bibtex file. Delighted that things have progressed thanks to you all and I learned s.th. again. Cheers, Birte On 1 December 2010 19:18, Uwe Stöhr wrote: > Am 01.12.2010 14:00, schrieb Birte Schoettker: > > > However, the last times I tried to use my added bibliography in Lyx via >> "Insert> Citation" it has been missing all entries in my *.bib file or >> jabref library alphabetically onwards from Wi*** to Z. >> The number of my references in my library is 1898 (!). Is there a >> cut-off I am not aware off? >> > > That there is a cutoff is new to me. Does it help if you split your > bib-file into 2 files and include them both to LyX? > If not, does it help if you are using another citation style file (not > harvard)? > > > Just for my curiosity: > > > Any help would be highly appreciated (my thesis is due in 4 weeks...yet >> again good timing, isn't it?:)). >> > > Respect! 1900s citation in one document is tough. Are you sure anybody > will/can have a look at so many citations? I mean its the duty of the > professors reviewing/supervising your thesis to look that the citations you > made are correct. This already a lot of work for 100 citations. How do they > do this for more than 1000? > > regards Uwe >
LyZ: lyxpipe changes in 2.0?
Hi, I use the LyZ FF addon to insert zotero references: https://addons.mozilla.org/en-US/firefox/addon/56806/ (btw, highly recommended!) I -think- it was working before on 2.0 svn, but I may be misremembering and it might have been 1.6... In any case one obvious problem seems to be that in LyZ preferences the default lyxpipe is: /home/user/.lyx/lyxpipe But looking for that file, I realized I have instead: /home/user/.lyx/lyxpipe.in /home/user/.lyx/lyxpipe.out I never cared to look for this before because it worked, it may have always been like that... Have there been changes on the way lyx uses lyxpipes? Could this be the reason it doesn't work? In any case, it could be a problem on the LyZ side of course. Here's a hint in that direction: http://www.klubko.net/wp/?page_id=945 "Now I have to port it to new Zotero API, but I just have so little time to look into it." This single addon makes lyx an order of magnitude more useful to me. Please let me know what I can do to help. Now that 2.0 is approaching rc, it'd be nice to have it working by then. -- Best, -Jose PS: looks like the entire LyZ architecture is a bit quirky: "After much opening and closing of programs I learned that I must open firefox *after* have my document is opened in Lyx. This was the critical step that I missed. Thanks again for writing this extremely useful program."" Jose Quesada, PhD. Research scientist, Max Planck Institute, Center for Adaptive Behavior and Cognition, Berlin http://www.josequesada.name/ http://twitter.com/Quesada
Re: LyX and Lithuanian language
I have not look to a LyX code. My behaviour was like a simple regular user - i set in a preferencies dialog some settings, and if that does not worked for me - i write a mail to a mailing list... And, when will be avalable LyX with more standart settings and with better suport different languages, like Lithuanian or Latvian? And, why is solution to set utf8x and L7x,T1 in preferencies so deprecated and should be do not used? But this solution is only, those was worked for me like expected... Another thing - when I set ASCII for Lithuanian language, error related to L7x still exists. Kt, 2010 12 02 08:22 +, Guenter Milde rašė: > On 2010-12-01, Egidijus Kamarauskas wrote: > > > Hallo. > > On my system have I installed texlive-lang-lithuanian package and I have > > on my machine lithuanian.ldf file (It is placed > > on /usr/share/texmf-texlive/tex/latex/lithuanian/lithuanian.ldf , so > > told me Synaptic). > > This looks OK. > > > I have tried to do this things like set Document>Settings>Language > > Lithuanian and without other > > \usepackage{lit...} in the preamble, > > This too. > > > either to set utf8x. Errors exists. I can not write Lithuanian texts. > > If I use English in settings, I can write this letters - ąčęėįšųūž, LyX > > compiles document very well, but Figure is Figure, Part is Part, and I > > can not change to right words. > > You could copy the code that defines the Lithuanian translations from > lithuanian.ldf to your preamble, but this would leave the hyphenation > at English, so better find another way. > > > Now I have attached my LyX file : > > newfile1.lyx with text. Try to set Lithuanian language and compile. > > Thanks for the file. I cannot compile here (without installing the > texlive-lang-lithuanian Debian package). > > However, View>Source with a tick at "complete sourec" revealed a strange > thing: > > The document preamble starts: > > \documentclass{article} > \usepackage[T1]{fontenc} > \usepackage[l7xenc]{inputenc} > \usepackage[lithuanian]{babel} > > But L7x is a *font* encoding, no *input* encoding. > Loading it with "inputenc" is a bug. > (The correct way would be ``\usepackage[L7x,T1]{fontenc}`` or > ``\usepackage[T1,L7x]{fontenc}``, the last option becomes the default > font encoding). > > This buggy line goes away, when I change > Document>Settings>Language>Encoding from "Language default" to ASCII. > > However, I found no occurence of the string "l7x" in the .lyx source > file, nor in LYX's languages file! > > Günter > >
Re: limit in number of reference entries in *.bib coming from jabref and used in lyx ? entries in reference list are cut off
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/01/2010 07:55 PM, Richard Heck wrote: > On 12/01/2010 08:00 AM, Birte Schoettker wrote: >> Hi all, >> >> I run Lyx 1.6.6.1 under Windows and use Jabref 2.6 to create my *.bib >> file for the references I use in Lyx via Insert>List/TOC>BiBTex >> Bibliography'. >> That all worked fine so far for the last 2 years, gaining insights >> about coding in jabref and dabandoning endnote for good on this way so >> far. >> >> What confuses me these days, is that I cannot recall to have changed >> anything relevant from last week to this in my *.bib reference file. I >> might have added about 10 more references or deleted a couple. >> However, the last times I tried to use my added bibliography in Lyx >> via "Insert> Citation" it has been missing all entries in my *.bib >> file or jabref library alphabetically onwards from Wi*** to Z. >> The number of my references in my library is 1898 (!). Is there a >> cut-off I am not aware off? >> > No, there's no cutoff. What's probably happening is that you have an > illegal character in one of your entries, probably the first one that > doesn't appear, and LyX is aborting the read when it sees it. This is a > pretty common problem. It often happens when people cut and paste > material from the web into JabRef and they get a funny quote or > something in there. If you can manage to launch LyX from a terminal, > then you will probably see the error message, which may also help. If > not, you can send me the file privately, and I'll figure it out. > >> Information that might be important: >> - coding of my library: Cp1252 >> > I don't know if that is an issue or not, but, ideally, BibTeX files > should always be pure ASCII. If you need non-ASCII characters, then use > the LaTeX equivalent. That directly leads me to a question I asked earlier, but did not find an answer to: How can I easily identify non-ASCII characters in the bibtex file? I struggled with this quite a lot (as I moved from a home made ACCESS database to Reference Manager database to bibtex), and I THINK my bibtex is now clean, but, I am not sure. Is there a script which I could run to identify non-ASCII characters in the bibtex file? I am running Linux. Cheers, Rainer > > Richard > - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz3Z9cACgkQoYgNqgF2egqHbgCfeNVuMEQkFiHOEKiP+wRfEQDr 4JcAoICYpdiUWWoguCl/2CBAxmZQZIZY =QwTs -END PGP SIGNATURE-
Re: LyX and Lithuanian language
On 2010-12-01, Egidijus Kamarauskas wrote: > Hallo. > On my system have I installed texlive-lang-lithuanian package and I have > on my machine lithuanian.ldf file (It is placed > on /usr/share/texmf-texlive/tex/latex/lithuanian/lithuanian.ldf , so > told me Synaptic). This looks OK. > I have tried to do this things like set Document>Settings>Language > Lithuanian and without other > \usepackage{lit...} in the preamble, This too. > either to set utf8x. Errors exists. I can not write Lithuanian texts. > If I use English in settings, I can write this letters - ąčęėįšųūž, LyX > compiles document very well, but Figure is Figure, Part is Part, and I > can not change to right words. You could copy the code that defines the Lithuanian translations from lithuanian.ldf to your preamble, but this would leave the hyphenation at English, so better find another way. > Now I have attached my LyX file : > newfile1.lyx with text. Try to set Lithuanian language and compile. Thanks for the file. I cannot compile here (without installing the texlive-lang-lithuanian Debian package). However, View>Source with a tick at "complete sourec" revealed a strange thing: The document preamble starts: \documentclass{article} \usepackage[T1]{fontenc} \usepackage[l7xenc]{inputenc} \usepackage[lithuanian]{babel} But L7x is a *font* encoding, no *input* encoding. Loading it with "inputenc" is a bug. (The correct way would be ``\usepackage[L7x,T1]{fontenc}`` or ``\usepackage[T1,L7x]{fontenc}``, the last option becomes the default font encoding). This buggy line goes away, when I change Document>Settings>Language>Encoding from "Language default" to ASCII. However, I found no occurence of the string "l7x" in the .lyx source file, nor in LYX's languages file! Günter