Re: New LyX Personal Package Archive: was Recommended third-party tools
On Sun, Feb 19, 2012 at 9:13 PM, Steve Litt wrote: >> [1] https://launchpad.net/~lyx-devel/+archive/release > > You should shout this from the rooftops. This should be on the LyX > Wiki's home page in +3 bold typesize. If this Personal Package Archive > (PPA) actually yields working LyXes, it changes everything. > I am doing my best. In any case, the packaging 'debian' dir is taken from Maverick and slightly tweaked to account for (some) changes in packaging in Oneiric. > From my perspective, a working PPA means no more stains on my > desk from the tears that I shed trying to ./configure;make;make install > and getting slapped down by dependencies at every turn. A working PPA > means an end to the annual pilgrimages to Xforms' gravestone, upon > which I placed flowers and mourned the hours lost to a particularly bad > Qt4 dependency way back in the early 1.6.x's. > I am glad if this can change your life (and spare you some flower expenses). :) > All this could mean I regularly have a modern and working LyX. > Please let me know how it works for you. Cheers Liviu > Maybe some day the PPA could encompass Red Hat and other types of > packages. This is really cool. Thank you! > > SteveT -- Do you know how to read? http://www.alienetworks.com/srtest.cfm http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
lyx latex-import problem
Hi I have a couple of hundred abstracts from a web form that produces simple LaTeX files. I have cat'ed them into one big LaTeX file and imported it to LyX. This works for the most part, but I have problem with \sindex that needs a option i [index_name] which is not recognized by LyX and therefor not put into ERT. I tried to get search replace it, but when LyX search within ERT it uses all memory and even if it seems to do the right thing it has been working on the file for a couple of hours... (file is only 300k and the box has 4G of ram, so something seems to be amiss) Is there some advice on how to do this more efficient? I could do it manually, but automated is better :) Linux and LyX 2.0.2 Ingar
New LyX Personal Package Archive: was Recommended third-party tools
On Sun, 19 Feb 2012 19:48:53 +0100 Liviu Andronic wrote: > On Sun, Feb 19, 2012 at 2:12 AM, Steve Litt [clip] > > On the other hand, Debian's more likely to > > have a *working* LyX :-) > > > This is hopefully changing. Now we have a PPA containing up-to-date > releases of LyX. [1] I will announce it on the list shortly. (The PPA > is still considered 'experimental' until more people test it and > provide positive feedback. Please do backups.) > > Liviu > > [1] https://launchpad.net/~lyx-devel/+archive/release Liviu, You should shout this from the rooftops. This should be on the LyX Wiki's home page in +3 bold typesize. If this Personal Package Archive (PPA) actually yields working LyXes, it changes everything. From my perspective, a working PPA means no more stains on my desk from the tears that I shed trying to ./configure;make;make install and getting slapped down by dependencies at every turn. A working PPA means an end to the annual pilgrimages to Xforms' gravestone, upon which I placed flowers and mourned the hours lost to a particularly bad Qt4 dependency way back in the early 1.6.x's. All this could mean I regularly have a modern and working LyX. Maybe some day the PPA could encompass Red Hat and other types of packages. This is really cool. Thank you! SteveT
Re: Mac-specific: tex2lyx won't run
On Feb 19, 2012, at 1:36 PM, stefano franchi wrote: > I am forwarding to the users' list. This problem starts to exceed my > lyx/Latex skills. What I can say is this: > > If I: > > 1. Import your file with the modified latex converter > > 2. Change fonts to non-latex > > 3. Select full-coverage unicode fonts like TeX Gyre Termes/Heros > > 4. Compile with xelatex > > Everything goes well. > > HOWEVER, the order of the 1-4 operations is crucial on my setup. If, > for instance, I import and then try to compile first (step 4), I get > the error you mention. After that, there is no way to get the file to > compile even after switching to non-latex fonts and selecting > appropriate fonts. I have to close the file and reimport it. > So: > > 1-2-3-4 works > 1-4-2-3-4 fails permanently > 1-2-4-3-4 fails permanently as well > > Closing the file after failure and trying again with the correct > sequence works. This may a lyx bug, I suspect. > > More skillful people may provide a deeper answer. Thanks for the problem-solving help again, Stefano. This worked. I had to guess in selecting fonts, as I have no idea what #3 amounts to. When I selected Palatino for serif, it went through. Thanks so much. I would appreciate help from anyone in identifying the offending character[s] so I don't have to jump through all these hoops every time I export from Scrivener/import to Lyx/compile. I don't know if Scrivener is source of the problem, if it's something I'm doing in the way I format in Scrivener--in one section of the paper I inserted a long-ish line centered on the page to mark a break between subsections of a section that I did not want to mark with subheadings--or if it's a problem with LyX. For now I'm grateful that Stefano has rescued me once again. Sincerely, -- Eric Weir Decatur, GA eew...@bellsouth.net "What does it mean...that the world is so beautiful?" - Mary Oliver
Re: Recommended third-party tools
Liviu, This is really great news! I've been longing for such a PPA. Thanks! Regards, Yihui -- Yihui Xie Phone: 515-294-2465 Web: http://yihui.name Department of Statistics, Iowa State University 2215 Snedecor Hall, Ames, IA On Sun, Feb 19, 2012 at 12:48 PM, Liviu Andronic wrote: > This is hopefully changing. Now we have a PPA containing up-to-date > releases of LyX. [1] I will announce it on the list shortly. (The PPA > is still considered 'experimental' until more people test it and > provide positive feedback. Please do backups.) > > Liviu > > [1] https://launchpad.net/~lyx-devel/+archive/release
Re: Recommended third-party tools
On Sun, Feb 19, 2012 at 2:12 AM, Steve Litt wrote: >> I'm working on creating the "perfect" step-by-step procedure for >> setting up a Linux workstation for scientific writing, based on LyX > It would be nice if you could use *bold* for each of the apps included in that page. This should improve the readability of the article. > 1) I'd recommend Ubuntu over Debian for two reasons: A) Ubuntu is > easier to get working with random hardware, and B) Ubuntu is likely to > have a newer LyX. On the other hand, Debian's more likely to have a > *working* LyX :-) > This is hopefully changing. Now we have a PPA containing up-to-date releases of LyX. [1] I will announce it on the list shortly. (The PPA is still considered 'experimental' until more people test it and provide positive feedback. Please do backups.) Liviu [1] https://launchpad.net/~lyx-devel/+archive/release
Re: Recommended third-party tools
On Sun, Feb 19, 2012 at 4:56 AM, Les Denham wrote: > Firstly, the version of Linux is not all that important. I've had good > experiences with Ubuntu in the past, but thanks to some idiotic (in my > opinion) decisions recently by the maintainers of both Gnome and KDE > and by Ubuntu for its default desktop, I've given up on Ubuntu, Gnome, > and KDE, all three of which I have used happily in the past. For the > average user now I would recommend Linux Mint (which just works even > more smoothly than Ubuntu) and, for those willing to learn a little or a > lot about what is behind the pretty windows, either Sabayon or Gentoo. > Whichever distro you choose, change the window manager to XFCE or LXDE. > It was somewhat implied, but to make it explicit, there is no need to drop Ubuntu because of the recent Gnome3/Unity fiasco: you can always change to Xubuntu (or Lubuntu). Personally I've been using Xfce for the past 5-7 years and I always found it---as far as the core apps are concerned---superior to Gnome 2. > If you are using "PDF for everything else" you definitely need > pdfimages (part of the Poppler library) and pdftk. > Another suggestion would be PDF Chain [1], a nice GUI interface to pdftk. Liviu [1] http://alternativeto.net/software/pdf-chain/
Re: Mac-specific: tex2lyx won't run
On Sun, Feb 19, 2012 at 11:00 AM, Eric Weir wrote:
>
> On Feb 19, 2012, at 9:54 AM, stefano franchi wrote:
>
> On Sun, Feb 19, 2012 at 5:13 AM, Eric Weir wrote:
>
>
> On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
>
>
> After both types of imports I get the following message: "Could not find
>
> LaTeX command for character''(code point 0x2028)
>
> Some characters of your document are probably not representable in the
>
> chosen encoding. Changing the document encoding to utf8 could help."
>
>
> I've verified that Scrivener uses Unicode UTF8.
>
>
> Perhaps you or someone one the list will know what the offending character
>
> is?
>
>
>
> Googling "codepoint 0x2028" I immediately located a previous post here by
>
> Jürgen responding to another user's query in which he said it was a line
>
> separater, and suggested doing a view > view source, locating the offending
>
> character, which would appear in red.
>
>
> I did that. There was only one instance in the source. But when I tried
>
> compiling after doing so I got the same error. This time I clicked on the
>
> "view complete log" button in the error window. I found six instances of the
>
> following error report:
>
>
> aa! LaTeX Error: Command \textquotedbl unavailable in encoding OT1., See the
>
> LaTeX manual or LaTeX Companion for explanation., Type H for
>
> immediate help., ... ,
>
> , l.380 Evident in \textquotedbl,
>
> {}Avoidable Losses\textquotedbl{}' alternative
>
>
> I am not really sure why you are getting this message---in particular
> I'm baffled by the OT1 reference. This is the old latex (tex) font
> encoding. It contains only the basic ASCII characters. Did this
> error(s) occur after you tried to compile correctly imported
> Scivener-Latex file? And if so, are you compiling with XeTex or Luatex
> or pdflatex?
>
>
> I've started over a couple times--fresh export from Scrivener, compile using
> latex (plain) modified with the 1e UTF8 coding.
>
> I've searched for the instances of the odd character combinations that in
> Scrivener I thought were single/double quote combinations but that view as
> source look more like a double quote/backtic combination, with the backtic
> sometimes inside and sometimes outside the double quote. As near as I could
> tell from the error messages, these were the offending characters. But after
> deleting them and inserting proper single/double quote combinations and
> compiling I got the same messages.
>
> One other thing. Jürgen said to view the source, look for the offending
> characters, and delete them. When I view the source I see on red error
> indication, not six, and the error is unrelated to the errors that are
> listed in the compile error window when I view the complete log, i.e., the
> one quoted above. It looks like this:
>
>
> \footnote{McNeil, Coppola, Radigan, \& Vasquez Heilig, 2008, 12--14.%
> } The apparent impact of the accountability system came to be widely
> discussed as ``the Texas miracle.'' As such it served as the model
> for other states and eventually the federal No Child Left Behind act.
> '>
>
>
> In case might be of help I'm attaching the complete compile error log from a
> XeTeX compile I tried and got the same error I get with LaTeX compiles. Also
> the Latex document as exported from Scrivener.
>
> Thanks for your help. I imagine you have more interesting or important
> things to be doing than this.
>
Eric,
I am forwarding to the users' list. This problem starts to exceed my
lyx/Latex skills. What I can say is this:
If I:
1. Import your file with the modified latex converter
2. Change fonts to non-latex
3. Select full-coverage unicode fonts like TeX Gyre Termes/Heros
4. Compile with xelatex
Everything goes well.
HOWEVER, the order of the 1-4 operations is crucial on my setup. If,
for instance, I import and then try to compile first (step 4), I get
the error you mention. After that, there is no way to get the file to
compile even after switching to non-latex fonts and selecting
appropriate fonts. I have to close the file and reimport it.
So:
1-2-3-4 works
1-4-2-3-4 fails permanently
1-2-4-3-4 fails permanently as well
Closing the file after failure and trying again with the correct
sequence works. This may a lyx bug, I suspect.
More skillful people may provide a deeper answer.
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: hyperlink from url fields in bibtex file
On 02/16/2012 04:29 PM, Csikos Bela wrote: Hello: I would like to include URL fields of the bibtex file in the bibliography as real clickable links. How can I do it? Currently the content of the URL fields looks like regular text. You need to use the \hyperlink command, I'd assume. Richard
Re: bibtex in UTF8 work? How to cancel bibtexkey escape in Lyx?
On 02/18/2012 04:22 AM, baiwensimi wrote: I found utf8 based bibtex works in XeTeX, even BibtexKey in utf8. But Lyx did not support it good when cite more than one items. the latex source code show that the utf8 bibtexkey will be escaped. How can I cancel this escape? Please post a small set of sample files that demonstrate the problem. Richard
Re: unnumbered chapter to toc
On 02/19/2012 08:52 AM, Ville Iiskola wrote:
Hi
i have unnumbered chapter and i add it to table of contents with command
\addcontentsline{toc}{chapter}{lähteet}
it appears in toc
"lähteet30"
when it should be
*lähteet30*
Can i change it some way?
Please post a short example file demonstrating the problem.
Richard
Re: Recommended third-party tools
On Sun, Feb 19, 2012 at 9:14 AM, David L. Johnson wrote: > On 02/18/2012 10:56 PM, Les Denham wrote: >> >> >> Firstly, the version of Linux is not all that important. I've had good >> experiences with Ubuntu in the past, but thanks to some idiotic (in my >> opinion) decisions recently by the maintainers of both Gnome and KDE >> and by Ubuntu for its default desktop, I've given up on Ubuntu, Gnome, >> and KDE, all three of which I have used happily in the past. For the >> average user now I would recommend Linux Mint (which just works even >> more smoothly than Ubuntu) and, for those willing to learn a little or a >> lot about what is behind the pretty windows, either Sabayon or Gentoo. >> Whichever distro you choose, change the window manager to XFCE or LXDE. > > > Amen to that. Gnome has, IMNSHO, shot themselves in the foot with a bloated > interface that doesn't work on a lot of hardware with their version 3. For > that reason, you do need to be careful to not use a distribution that only > uses Gnome. It was a long annoying process for me to switch over after an > upgrade dumped me into Gnome 3. Xfce is fine, though, so and distribution > that allows you to choose will be good. Frankly, I don't know what Kde did, > but my advice is to avoid Gnome. > This is starting to be more and more off-topic, but here are my 2 cents on distros: I'm very happy with KDE and have been using it since version 3.4. However, Kubuntu (Kde-based ubuntu distribution) is terrible and will probably get worse now that Canonical has moved the only fully paid maintainer to other projects. By "terrible" i mean that the twice yearly major upgrades would routinely break my X11 setup, which meant manually tweaking the xorg.conf file every time. Definitely not fun (http://xkcd.com/963/ pretty much describes my life under kubuntu). Switching to Archlinux solved all my problems, however. Kde is rock-solid and fast (even on not so recent hardware). I never had any problems Stefano > -- > > David L. Johnson > > When you are up to your ass in alligators, it's hard to remember that > your initial objective was to drain the swamp. > -- LBJ > -- __ 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: Recommended third-party tools
On 02/18/2012 10:56 PM, Les Denham wrote: Firstly, the version of Linux is not all that important. I've had good experiences with Ubuntu in the past, but thanks to some idiotic (in my opinion) decisions recently by the maintainers of both Gnome and KDE and by Ubuntu for its default desktop, I've given up on Ubuntu, Gnome, and KDE, all three of which I have used happily in the past. For the average user now I would recommend Linux Mint (which just works even more smoothly than Ubuntu) and, for those willing to learn a little or a lot about what is behind the pretty windows, either Sabayon or Gentoo. Whichever distro you choose, change the window manager to XFCE or LXDE. Amen to that. Gnome has, IMNSHO, shot themselves in the foot with a bloated interface that doesn't work on a lot of hardware with their version 3. For that reason, you do need to be careful to not use a distribution that only uses Gnome. It was a long annoying process for me to switch over after an upgrade dumped me into Gnome 3. Xfce is fine, though, so and distribution that allows you to choose will be good. Frankly, I don't know what Kde did, but my advice is to avoid Gnome. -- David L. Johnson When you are up to your ass in alligators, it's hard to remember that your initial objective was to drain the swamp. -- LBJ
unnumbered chapter to toc
Hi
i have unnumbered chapter and i add it to table of contents with command
\addcontentsline{toc}{chapter}{lähteet}
it appears in toc
"lähteet30"
when it should be
lähteet30
Can i change it some way?
Ville
Re: How to force tex2lyx to read unicode (from within Lyx)?
Guenter Milde wrote: > On 2012-02-15, Georg Baum wrote: >> 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. > > It is the other way round: using xetex or luatex is also possible without > use_non_tex_fonts (which actually means use_fontspec). OTOH, with > use_non_tex_fonts True, it one of xetex or luatex must be used. For luatex I agree, but for xetex I don't believe that you are right. Do you have an example .lyx file, where use_non_tex_fonts is false, but xetex is still used? If you are right, the patch introduces a regression. Georg
Re: Mac-specific: tex2lyx won't run
On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
> After both types of imports I get the following message: "Could not find
> LaTeX command for character''(code point 0x2028)
> Some characters of your document are probably not representable in the chosen
> encoding. Changing the document encoding to utf8 could help."
>
> I've verified that Scrivener uses Unicode UTF8.
>
> Perhaps you or someone one the list will know what the offending character is?
Googling "codepoint 0x2028" I immediately located a previous post here by
Jürgen responding to another user's query in which he said it was a line
separater, and suggested doing a view > view source, locating the offending
character, which would appear in red.
I did that. There was only one instance in the source. But when I tried
compiling after doing so I got the same error. This time I clicked on the "view
complete log" button in the error window. I found six instances of the
following error report:
aa! LaTeX Error: Command \textquotedbl unavailable in encoding OT1., See the
LaTeX manual or LaTeX Companion for explanation., Type H for
immediate help., ... ,
, l.380 Evident in \textquotedbl,
{}Avoidable Losses\textquotedbl{}' alternative
It looked to me like these were situations in which I used an apostrophe in
combination with a double quote. I searched for that combination and found that
some occurrences were different than others. I don't know how to describe the
difference except to say some did not look like a standard single/double quote
combination. More like a doublequote/right-leaning backtic combination.
I lost count, but I think there were six of them. I deleted them and replaced
them with a doublequote/singlequote combination. Tried compiling again and got
the same errors.
I am at a loss. Help would be appreciated.
Thanks,
--
Eric Weir
Decatur, GA
eew...@bellsouth.net
"We do not inherit the earth from our ancestors,
we borrow it from our children."
- Chief Seattle.
