Re: LyX 2.0.3 Sources Available
Am 20.02.2012 um 23:55 schrieb Cor Blom: > Op maandag 20 februari 2012 23:02:38 schreef Cor Blom: >> Op maandag 20 februari 2012 22:39:46 schreef Liviu Andronic: >>> On Mon, Feb 20, 2012 at 10:19 PM, Cor Blom wrote: The only way I can understand that is that lyx is looking in /usr/share/myspell for the dictionaries. >>> >>> This is what seems to happen on Ubuntu Lucid. I have installed LyX >>> 2.0.3 with a clean profile (no manual hunspell path specified) and LyX >>> now automatically detects the hunspell dictionaries located in: >>> liv@liv-laptop:~$ ls /usr/share/myspell -l >>> total 8 >>> drwxr-xr-x 2 root root 4096 2012-02-08 09:24 dicts >>> drwxr-xr-x 3 root root 4096 2010-04-29 17:45 infos >>> >>> And I have no symlink specified here: >>> liv@liv-laptop:~$ ls /usr/share/lyx/dicts >>> ls: cannot access /usr/share/lyx/dicts: No such file or directory >> >> on openSUSE I still have to tell lyx where the hunspell dicts can be found >> (either via lyxrc.dist or via symlinks). Will investigate later when I have >> some time. It is not really a problem as the old method was working fine. >> > Ok, found the difference between specifying the hunspell dicts path > explicitly > and not. When the path is explicitly/manually given, that path is used (in my > case /usr/share/myspell), but when the path is left empty (and I used a clean > profile) /usr/share/myspell/dicts is used. That directory does not exist. > > So when no manual hunspell path is specified, lyx on opensuse is looking in > the wrong directory (adding "dicts" to the path). I've introduced the lookup for dicts in /usr/share/myspell. At that time I thought about a configure option too - but I didn't introduce one. The "dicts" sub dir directory addition I got from the rpm file list of the dictionary packages. So, yes, effectively LyX looks for the hunspell dictionaries in "/usr/share/myspell/dicts" as a last resort. The other places LyX is looking for system dictionaries is the directory dicts in the LyX system dir. For your rpm this would be "/usr/share/lyx/dicts" I'd guess. Stephan
Re: Windows Installer could use work: must set miktex packages
I always set MiKTeX to "no" before a LyX install, but that's a personal preference. The cardinal objection I've heard to it as a default is that a new user might be confused when LyX "installed" but then couldn't open its help files or create new documents. The LyX GUI doesn't open until the configuration script is done, so if you saw latex.exe spawning and dying repeatedly in the task manager, it sounds as if things were working correctly. You just need LOTS of patience. Regarding "ask" mode, any chance the dialog box was opening behind a window? I think you need to install both LyX and MiKTeX for "all users" in a shared machine/laboratory setup. Once installed, I think MiKTeX will let users individually install packages on a per user basis (but I'm not positive, as I've only used it on single-user systems). Last, installing all packages by default will cause huge frustration (and could bring the Internet to its knees). Paul
[patch] a new module for fancyvrb to fix infinite loop bug #7648
The attached module is written to support the Verbatim environment of the LaTeX-package fancyvrb. I
wrote it to be able to fix
www.lyx.org/trac/ticket/7648
that sends LyX into an infinite loop since tex2lyx cannot handle files using fancyvrb. tex2lyx can
of course not support every package but in this case an infinite loop is not acceptable.
With the module I could add tex2lyx support for fancyvrb and thus fix the bug but I'm not sure if
this way is the best. Comments are welcome.
thanks and regards
Uwe
Index: Verbatim.module
===
--- Verbatim.module (revision 0)
+++ Verbatim.module (working copy)
@@ -0,0 +1,39 @@
+#\DeclareLyXModule{Verbatim advanced}
+#DescriptionBegin
+#Define a style for fancyvrb's enhanced Verbatim enviroment.
+#See the Verbatim_advanced example file for a detailed description.
+#DescriptionEnd
+#Authors: Uwe Stöhr
+
+Format 36
+
+AddToPreamble
+ \usepackage{fancyvrb}
+EndPreamble
+
+Style "Verbatim advanced"
+ Category MainText
+ LatexType Environment
+ LatexName Verbatim
+ Margin First_Dynamic
+ LabelType static
+ LabelString "Verbatim advanced:"
+ OptionalArgs 1
+ NextNoIndent 1
+ ParbreakIsNewline 1
+ FreeSpacing 1
+ PassThru 1
+ NewLine 0
+ LabelSep xx
+ ParIndent MMM
+ ParSkip 0.4
+ TopSep 0.7
+ BottomSep 0.7
+ ParSep 0.3
+ Align Left
+ AlignPossible Left
+ LabelFont
+ Series Bold
+ EndFont
+End
+
Index: Verbatim.module
===
--- Verbatim.module (revision 0)
+++ Verbatim.module (working copy)
Property changes on: Verbatim.module
___
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Re: LyX 2.0.3 Sources Available
Op maandag 20 februari 2012 23:02:38 schreef Cor Blom: > Op maandag 20 februari 2012 22:39:46 schreef Liviu Andronic: > > On Mon, Feb 20, 2012 at 10:19 PM, Cor Blom wrote: > > > The only way I can understand that is that lyx is looking in > > > /usr/share/myspell for the dictionaries. > > > > This is what seems to happen on Ubuntu Lucid. I have installed LyX > > 2.0.3 with a clean profile (no manual hunspell path specified) and LyX > > now automatically detects the hunspell dictionaries located in: > > liv@liv-laptop:~$ ls /usr/share/myspell -l > > total 8 > > drwxr-xr-x 2 root root 4096 2012-02-08 09:24 dicts > > drwxr-xr-x 3 root root 4096 2010-04-29 17:45 infos > > > > And I have no symlink specified here: > > liv@liv-laptop:~$ ls /usr/share/lyx/dicts > > ls: cannot access /usr/share/lyx/dicts: No such file or directory > > on openSUSE I still have to tell lyx where the hunspell dicts can be found > (either via lyxrc.dist or via symlinks). Will investigate later when I have > some time. It is not really a problem as the old method was working fine. > Ok, found the difference between specifying the hunspell dicts path explicitly and not. When the path is explicitly/manually given, that path is used (in my case /usr/share/myspell), but when the path is left empty (and I used a clean profile) /usr/share/myspell/dicts is used. That directory does not exist. So when no manual hunspell path is specified, lyx on opensuse is looking in the wrong directory (adding "dicts" tot the path). Cor
Re: [patch] use libmagic for file format detection
Le 20/02/2012 17:47, Richard Heck a écrit : In that case, it's obviously an improvement over what we have. There must be some kind of mime-detection software on Windows, right? Or maybe some QMime? It looks like it will appear in qt5, and there for we will be able to use it in 2016 :) JMarc
Re: LyX 2.0.3 Sources Available
Op maandag 20 februari 2012 22:39:46 schreef Liviu Andronic: > On Mon, Feb 20, 2012 at 10:19 PM, Cor Blom wrote: > > The only way I can understand that is that lyx is looking in > > /usr/share/myspell for the dictionaries. > > This is what seems to happen on Ubuntu Lucid. I have installed LyX > 2.0.3 with a clean profile (no manual hunspell path specified) and LyX > now automatically detects the hunspell dictionaries located in: > liv@liv-laptop:~$ ls /usr/share/myspell -l > total 8 > drwxr-xr-x 2 root root 4096 2012-02-08 09:24 dicts > drwxr-xr-x 3 root root 4096 2010-04-29 17:45 infos > > And I have no symlink specified here: > liv@liv-laptop:~$ ls /usr/share/lyx/dicts > ls: cannot access /usr/share/lyx/dicts: No such file or directory > on openSUSE I still have to tell lyx where the hunspell dicts can be found (either via lyxrc.dist or via symlinks). Will investigate later when I have some time. It is not really a problem as the old method was working fine. Cor
Re: [patch] use libmagic for file format detection
On 02/19/2012 11:56 AM, Georg Baum wrote: Richard Heck wrote: On 02/19/2012 07:38 AM, Georg Baum wrote: I do not know whether it is possible/how easy it is to build libmagic on windows. That's the big question, obviously. What does the patch do if we don't have libmagic? (I'm sure I could figure it out, but it's a big patch) It falls back to the old code. Also if libmagic does not find a known format. In that case, it's obviously an improvement over what we have. There must be some kind of mime-detection software on Windows, right? Richard
Re: LyX 2.0.3 Sources Available
On 02/20/2012 04:30 PM, Pavel Sanda wrote: Cor Blom wrote: But I was set on the wrong foot by this paragraph in ANNOUNCE: - Add the directory /usr/share/myspell as default location for dictionary lookup of hunspell spell checker backend (a common location on linux). Detect value change of preferences path to hunspell dictionaries to avoid the need for a restart. This is related to bug 7884. I suspect LyX is now watching both locations (untested), anyway RELEASE-NOTES should be updated to the current status once branch is opened again... I never use spellcheck so don't know what changes have or have not happened here. Can you update this when we're ready? Richard
Re: LyX 2.0.3 Sources Available
On Mon, Feb 20, 2012 at 10:19 PM, Cor Blom wrote: > The only way I can understand that is that lyx is looking in > /usr/share/myspell for the dictionaries. > This is what seems to happen on Ubuntu Lucid. I have installed LyX 2.0.3 with a clean profile (no manual hunspell path specified) and LyX now automatically detects the hunspell dictionaries located in: liv@liv-laptop:~$ ls /usr/share/myspell -l total 8 drwxr-xr-x 2 root root 4096 2012-02-08 09:24 dicts drwxr-xr-x 3 root root 4096 2010-04-29 17:45 infos And I have no symlink specified here: liv@liv-laptop:~$ ls /usr/share/lyx/dicts ls: cannot access /usr/share/lyx/dicts: No such file or directory Liviu
Re: LyX 2.0.3 Sources Available
Cor Blom wrote: > But I was set on the wrong foot by this paragraph in ANNOUNCE: > > - Add the directory /usr/share/myspell as default location for dictionary > lookup of hunspell spell checker backend (a common location on linux). > Detect value change of preferences path to hunspell dictionaries > to avoid the need for a restart. This is related to bug 7884. I suspect LyX is now watching both locations (untested), anyway RELEASE-NOTES should be updated to the current status once branch is opened again... Pavel
Re: LyX 2.0.3 Sources Available
Op maandag 20 februari 2012 21:49:18 schreef Pavel Sanda: > Cor Blom wrote: > > Is this a bug, or is it intended to work this way? > > RELEASE-NOTES clearly states: > System-wide hunspell dictionaries are in standard Linux installs > looked up at /usr/local/share/lyx/dicts/. > I missed that. Sorry. But I was set on the wrong foot by this paragraph in ANNOUNCE: - Add the directory /usr/share/myspell as default location for dictionary lookup of hunspell spell checker backend (a common location on linux). Detect value change of preferences path to hunspell dictionaries to avoid the need for a restart. This is related to bug 7884. The only way I can understand that is that lyx is looking in /usr/share/myspell for the dictionaries. Cor
Re: LyX 2.0.3 Sources Available
Pavel Sanda wrote: > Cor Blom wrote: > > Is this a bug, or is it intended to work this way? > > RELEASE-NOTES clearly states: > System-wide hunspell dictionaries are in standard Linux installs > looked up at /usr/local/share/lyx/dicts/. Reading again, its not perhaps best written, since the the prefix can be different at different distros... > > Pavel
Re: LyX 2.0.3 Sources Available
Cor Blom wrote: > Is this a bug, or is it intended to work this way? RELEASE-NOTES clearly states: System-wide hunspell dictionaries are in standard Linux installs looked up at /usr/local/share/lyx/dicts/. Pavel
Re: LyX 2.0.3 Sources Available
Op maandag 20 februari 2012 14:59:08 schreef Pavel Sanda: > Cor Blom wrote: > > It is building fine on all version of openSUSE. But I have a problem > > with > > hunspell. If I understand correctly, user or packager no longer have to > > give an explicit directory for the hunspell dictionaries, because > > /usr/share/myspell is used by default. So I removed the line > > '\hunspelldir_path "/usr/share/myspell"' from lyxrc.dist. But in the > > resulting package hunspell is no longer working and the user has to > > provide the path to the dictionaries himself. > > This issue should be fixed if you create softlink (gentoo solution) > /usr/share/lyx/dicts -> /usr/share/myspell/ (or whatever location you use) > /usr/share/lyx/thes -> /usr/share/myspell/ > It is working that way. Thanks! Is this a bug, or is it intended to work this way? Cor
Re: 2 trunk compilation errors with CMake in release mode
Am 17.02.2012 15:16, schrieb Vincent van Ravesteijn: This is something we discussed also previously. Yes. Why don't you create two MSVC projects. One for trunk and one for branch ? I already have them. I don't understand your concerns. We discussed the topic already and as result peter created the batch file. I use it daily and I think others will too. I only started this thread about a compiler flag. This flag can also be set in an IDE but that was not the question, it was about what to set by default. regards Uwe
Question about german dictionaries
Hi, I got bug report about german hunspell dictionary not working. LyX looks for de_DE.dic/aff while de_DE_frami.dic/acc is installed. How is this in other distros/archs - should we know about this or its just myspell packaging issue? One (no more working) link shows that such naming was used officially http://extensions.services.openoffice.org/de/project/dict-de_DE_frami Whats the Debian/Fedora/Mac solution? Pavel
Re: LyX 2.0.3 Sources Available
Cor Blom wrote: > It is building fine on all version of openSUSE. But I have a problem with > hunspell. If I understand correctly, user or packager no longer have to give > an explicit directory for the hunspell dictionaries, because > /usr/share/myspell is used by default. So I removed the line > '\hunspelldir_path "/usr/share/myspell"' from lyxrc.dist. But in the > resulting > package hunspell is no longer working and the user has to provide the path to > the dictionaries himself. This issue should be fixed if you create softlink (gentoo solution) /usr/share/lyx/dicts -> /usr/share/myspell/ (or whatever location you use) /usr/share/lyx/thes -> /usr/share/myspell/ Pavel
Re: LyX 2.0.3 Sources Available
Op zondag 19 februari 2012 11:18:44 schreef Richard Heck: > LyX 2.0.3 source tarballs are available from: > http://frege.brown.edu/lyx/ > Please let me know if there are any difficulties. I'll plan to release > late this week (Friday or Saturday) if there are not. > > Please note that branch is still closed. > > Richard It is building fine on all version of openSUSE. But I have a problem with hunspell. If I understand correctly, user or packager no longer have to give an explicit directory for the hunspell dictionaries, because /usr/share/myspell is used by default. So I removed the line '\hunspelldir_path "/usr/share/myspell"' from lyxrc.dist. But in the resulting package hunspell is no longer working and the user has to provide the path to the dictionaries himself. Cor P.S. My lyx testing project can be found here: https://build.opensuse.org/package/show?package=lyx&project=home%3Acornelisbb%3Alyx- unstable
Re: LyX 2.0.3 Sources Available
On Mon, Feb 20, 2012 at 10:21 AM, Jean-Marc Lasgouttes wrote: > Does it make sense on ubuntu to use aspell and hunspell if enchant is > configured? I would think this adds unnecessary dependencies. Or is it what > the official builds do? > Debian builds come with support for Enchant only, but I'm unhappy with this. Although Enchant supports both Aspell and Hunspell, it does add an additional---and somewhat obscure---configuration hiccup. I find it nice for users to be able to select their spell checker via the LyX Prefs---in the end this is why LyX supports them all. The added deps are not huge while most users probably have them already. Cheers Liviu
Re: LyX 2.0.3 Sources Available
Am 20.02.2012 um 10:41 schrieb Stephan Witt: > Am 20.02.2012 um 10:21 schrieb Jean-Marc Lasgouttes: > >> Le 19/02/2012 21:40, Liviu Andronic a écrit : >>> On Sun, Feb 19, 2012 at 5:18 PM, Richard Heck wrote: LyX 2.0.3 source tarballs are available from: >>> Ubuntu binaries are available on the LyX Team PPA [1]. Should anyone >>> trying the PPA encounter any issues with those, please let me know. >>> [1] https://launchpad.net/~lyx-devel/+archive/release >>> >>> Configuration >>> Host type:x86_64-pc-linux-gnu >>> Special build flags: build=release warnings use-aspell >>> use-enchant use-hunspell >> >> Does it make sense on ubuntu to use aspell and hunspell if enchant is >> configured? I would think this adds unnecessary dependencies. Or is it what >> the official builds do? > > Yes, I think so. enchant has it's own drawbacks, AFAIK. Sorry, that was not clear. I think LyX should use at least pure hunspell if possible. I don't know if official builds provide enchant, aspell and hunspell. > I remember reports of problems with compound words and word delimiters with > enchant+hunspell not reproducible with pure hunspell. > > Stephan >
Re: LyX 2.0.3 Sources Available
Am 20.02.2012 um 10:21 schrieb Jean-Marc Lasgouttes: > Le 19/02/2012 21:40, Liviu Andronic a écrit : >> On Sun, Feb 19, 2012 at 5:18 PM, Richard Heck wrote: >>> LyX 2.0.3 source tarballs are available from: >>> >> Ubuntu binaries are available on the LyX Team PPA [1]. Should anyone >> trying the PPA encounter any issues with those, please let me know. >> [1] https://launchpad.net/~lyx-devel/+archive/release >> >> Configuration >> Host type:x86_64-pc-linux-gnu >> Special build flags: build=release warnings use-aspell >> use-enchant use-hunspell > > Does it make sense on ubuntu to use aspell and hunspell if enchant is > configured? I would think this adds unnecessary dependencies. Or is it what > the official builds do? Yes, I think so. enchant has it's own drawbacks, AFAIK. I remember reports of problems with compound words and word delimiters with enchant+hunspell not reproducible with pure hunspell. Stephan
Re: LyX 2.0.3 Sources Available
Le 19/02/2012 21:40, Liviu Andronic a écrit : On Sun, Feb 19, 2012 at 5:18 PM, Richard Heck wrote: LyX 2.0.3 source tarballs are available from: Ubuntu binaries are available on the LyX Team PPA [1]. Should anyone trying the PPA encounter any issues with those, please let me know. [1] https://launchpad.net/~lyx-devel/+archive/release Configuration Host type:x86_64-pc-linux-gnu Special build flags: build=release warnings use-aspell use-enchant use-hunspell Does it make sense on ubuntu to use aspell and hunspell if enchant is configured? I would think this adds unnecessary dependencies. Or is it what the official builds do? JMarc
