Re: Hunspell dictionaries browser can't be opened
Le 19/09/2018 à 20:34, Wolfgang Engelmann a écrit : Clicking in the field where the path is to be set does not do anything, the cursor does not appear in this field, in contrast to all the other fields. Wolfgang Is hunspell enabled in your build? What OS is that? JMarc
Re: Hunspell dictionaries browser can't be opened
On 19.09.2018 19:16, Jürgen Spitzmüller wrote: Am Mittwoch, den 19.09.2018, 15:49 +0200 schrieb Wolfgang Engelmann: I try to insert the path to the Hunspell dictionaries, but the browse... can't be opened (clicking does not do anything). All the other browse... are klickable. I am using Lyx 2.3.0 under Linux-Mint. Did you check the file dialog does not hide behind the main window? Jürgen Clicking in the field where the path is to be set does not do anything, the cursor does not appear in this field, in contrast to all the other fields. Wolfgang What could I do? Wolfgang
Re: Hunspell dictionaries browser can't be opened
Am Mittwoch, den 19.09.2018, 15:49 +0200 schrieb Wolfgang Engelmann: > I try to insert the path to the Hunspell dictionaries, but the > browse... > can't be opened (clicking does not do anything). All the other > browse... > are klickable. > > I am using Lyx 2.3.0 under Linux-Mint. Did you check the file dialog does not hide behind the main window? Jürgen > > What could I do? > > Wolfgang > signature.asc Description: This is a digitally signed message part
Hunspell dictionaries browser can't be opened
I try to insert the path to the Hunspell dictionaries, but the browse... can't be opened (clicking does not do anything). All the other browse... are klickable. I am using Lyx 2.3.0 under Linux-Mint. What could I do? Wolfgang
Re: Supporting the cleverref package?
Another nice aspect of cleveref is, that it automatically calls references to appendix sections "appendix". This may become important, when I later decide to move whole sections to the appendix. On Wed, Sep 19, 2018 at 3:32 PM Klaus-Dieter Bauer < bauer.klaus.die...@gmail.com> wrote: > On Mon, Sep 17, 2018 at 5:09 PM Richard Kimberly Heck > wrote: > >> On 9/17/18 6:11 AM, Klaus-Dieter Bauer wrote: >> > Thanks, I wasn't aware of \prettyref support :) >> > >> > For my purposes this fits the bill, as the commands seem to be >> > effectively interchangeable and only really differ in how the >> > formatting is determined. >> > Well, except for a possibility to make \cref automatically capitalize >> > at the beginning of sentences, as done by \prettyref, but I found that >> > sentences rarely start with references anyway. >> >> >> Well, refstyle does support the capitalization thing, and plurals too. >> Is there some reason you don't want to use it? >> >> Riki >> > > Mostly cross-compatibility with latex export/import and editing the plain > latex later. > > The cleveref package currently implements the best logic, as it bases the > formatting on the actual target of the reference, rather than the name of > the label. For instance, if I decide to change a theorem to a result > environment while end-formatting the plain LaTeX source, both refstyle and > prettyref would either > >- require replacing all references in the document (error-prone for >multi-file documents), or >- produce incorrectly formatted references. > > - Klaus > >
Re: Supporting the cleverref package?
On Mon, Sep 17, 2018 at 5:09 PM Richard Kimberly Heck wrote: > On 9/17/18 6:11 AM, Klaus-Dieter Bauer wrote: > > Thanks, I wasn't aware of \prettyref support :) > > > > For my purposes this fits the bill, as the commands seem to be > > effectively interchangeable and only really differ in how the > > formatting is determined. > > Well, except for a possibility to make \cref automatically capitalize > > at the beginning of sentences, as done by \prettyref, but I found that > > sentences rarely start with references anyway. > > > Well, refstyle does support the capitalization thing, and plurals too. > Is there some reason you don't want to use it? > > Riki > Mostly cross-compatibility with latex export/import and editing the plain latex later. The cleveref package currently implements the best logic, as it bases the formatting on the actual target of the reference, rather than the name of the label. For instance, if I decide to change a theorem to a result environment while end-formatting the plain LaTeX source, both refstyle and prettyref would either - require replacing all references in the document (error-prone for multi-file documents), or - produce incorrectly formatted references. - Klaus
