Re: Exporting ePub / XML: always SIGSEV
Dear Eberhard, thanks very much for the promising hint and sorry for answering late: I am still trying to understand lwarp. It is already installed, and also the lwarpmk utility is set up, but I think I need a little time to get through this. I will give you a feedback when I have got it. All best Jess Am 27. Apr. 2019, 16:49 +0200 schrieb Dr Eberhard Lisse : > Have you looked at lwarp on CTAN? > > el > > On 2019-04-26 19:48 , jezZiFeR wrote: > > Dear Anders, > > > > thank you so much! I have now found a possibility to use ePub. It is > > still not perfect and up to now is not useful for publishing etc., but > > for private use it is fine. The following seems to work for me: > > > > export–LyXhtml (here LyX is not getting a SIGSEV) > > then I convert the XHTML-file in Calibre to ePub > > > > Calibre is really extremely useful… I think I will try a little bit > > around with LyX and Calibre in the next time, but for the moment this > > works for me. > > > > All best > > Jess >
Re: Help for Help > was Fwd: Lyx Help in German, although set for English
On 2019-05-02, Wolfgang Engelmann wrote: > I wanted to compare my settings of the Lyx document with the one of a > Help file (i have chosen Users Guide). However, the Text there is in > German, although I have set the language under > tools>preferences>language settings>English Under normal conditions, this would make the menu entries under Help>... look for the English version of the documentation. OTOH, it will have no influence on the files opened with File>Open. (There, you can select the several language subdirectories like "de/" for German.) What is the proposed path if you try "File>Save As" on the opened UserGuide with German text? > and under Document settings>Language>English (USA). With this setting, you change the language declaration, i.e. you tell LyX which language's conventions to use when processing the document. This influences hyphenation, auto-generated text parts and spell-checking but does not traslate the literal text. Sometimes, even more changes occure, e.g. changing Document_settings>Language> to Greek will render the output in Greek letters (unless you are using non-TeX fonts). Günter
Help for Help > was Fwd: Lyx Help in German, although set for English
Forwarded Message Subject:Lyx Help in German, although set for English Date: Wed, 10 Apr 2019 10:18:57 +0200 From: Wolfgang Engelmann To: lyx-users@lists.lyx.org I wanted to compare my settings of the Lyx document with the one of a Help file (i have chosen Users Guide). However, the Text there is in German, although I have set the language under tools>preferences>language settings>English and under Document settings>Language>English (USA). What is wrong? Wolfgang I resent this, since I would very much like to know, why I do get most of the German Help files in Lyx, although I have set (I think) everything in settings and tools in English (tried also in Tools>preferences>language settings> automatic switched to always babel) and the titles are all shown in English. Exception: The contents are In English in 'Latex configurations' and some of the specific manuals Wolfgang
Re: hyphenation point in bib file
On 02.05.19 09:21, Stephan Witt wrote:
Am 02.05.2019 um 08:27 schrieb Wolfgang Engelmann :
On 01.05.19 22:27, Paul A. Rubin wrote:
On 5/1/19 7:23 AM, Wolfgang Engelmann wrote:
Does somebody know how I can use a hyphenation point in a bib file? I use a two
column page layout in my lax document and a word is not broken, thus running in
the next column.
Wolfgang
You can insert {\-} in the .bib file to indicate an optional hyphenation point.
Paul
Thanks, Axel and Paul. Inserting just ~ did not work, {\~}worked in this case:
Trans{\-}lation-independent circadian control of the cell cycle in a
unicellular photosynthetic eukaryote
Miyagishima, Shin-ya et al. (2014). “Trans-
lation-independent circadian control of
the cell cycle in a unicellular photosyn-
thetic eukaryote.” In: Nature communi-
cations 5, p. 3807.
but not here
A transcriptionally and functionally distinct PD-1,
{\-}javax.xml.bind.JAXBElement{\-}@7a062e7f, CD8,{\-}
javax.xml.bind.JAXBElement{\-}@2110cbd6, T cell pool with predictive potential
in non-small-cell lung cancer treated with PD-1 blockade.
I don't believe this title is correct. It looks like the (wrong) output of a
text-processing utility.
Stephan
I thought so too, but it is correct
Wolfgang
Thommen, Daniela S. et al. (2018). “A tran-
scriptionally and functionally distinct
PD-1, javax.xml.bind.JAXBElement@7a062e7f,
CD8, javax.xml.bind.JAXBElement@2110cbd6,
T cell pool with predictive potential in
non-small-cell lung cancer treated with
PD-1 blockade.” In: Nature medicine 24,
pp. 994–1004.
Wang, Yaping et al. (2017). “Upregula-
tion of circadian gene ’hClock’ contribu-
tion to metastasis of colorectal cancer.”
In: International journal of oncology 50,
pp. 2191–2199.
I can live with it, since this citation happens to be in the right column and
is still readable.
Wolfgang
Re: hyphenation point in bib file
Am 02.05.2019 um 08:27 schrieb Wolfgang Engelmann :
>
>
>
> On 01.05.19 22:27, Paul A. Rubin wrote:
>> On 5/1/19 7:23 AM, Wolfgang Engelmann wrote:
>>> Does somebody know how I can use a hyphenation point in a bib file? I use a
>>> two column page layout in my lax document and a word is not broken, thus
>>> running in the next column.
>>>
>>> Wolfgang
>>>
>> You can insert {\-} in the .bib file to indicate an optional hyphenation
>> point.
>>
>> Paul
>>
> Thanks, Axel and Paul. Inserting just ~ did not work, {\~}worked in this case:
>
> Trans{\-}lation-independent circadian control of the cell cycle in a
> unicellular photosynthetic eukaryote
>
> Miyagishima, Shin-ya et al. (2014). “Trans-
> lation-independent circadian control of
> the cell cycle in a unicellular photosyn-
> thetic eukaryote.” In: Nature communi-
> cations 5, p. 3807.
>
> but not here
>
> A transcriptionally and functionally distinct PD-1,
> {\-}javax.xml.bind.JAXBElement{\-}@7a062e7f, CD8,{\-}
> javax.xml.bind.JAXBElement{\-}@2110cbd6, T cell pool with predictive
> potential in non-small-cell lung cancer treated with PD-1 blockade.
I don't believe this title is correct. It looks like the (wrong) output of a
text-processing utility.
Stephan
>
> Thommen, Daniela S. et al. (2018). “A tran-
> scriptionally and functionally distinct
> PD-1, javax.xml.bind.JAXBElement@7a062e7f,
> CD8, javax.xml.bind.JAXBElement@2110cbd6,
> T cell pool with predictive potential in
> non-small-cell lung cancer treated with
> PD-1 blockade.” In: Nature medicine 24,
> pp. 994–1004.
>
> Wang, Yaping et al. (2017). “Upregula-
> tion of circadian gene ’hClock’ contribu-
> tion to metastasis of colorectal cancer.”
> In: International journal of oncology 50,
> pp. 2191–2199.
>
> I can live with it, since this citation happens to be in the right column and
> is still readable.
>
> Wolfgang
>
>
Re: hyphenation point in bib file
On 01.05.19 22:27, Paul A. Rubin wrote:
On 5/1/19 7:23 AM, Wolfgang Engelmann wrote:
Does somebody know how I can use a hyphenation point in a bib file? I
use a two column page layout in my lax document and a word is not
broken, thus running in the next column.
Wolfgang
You can insert {\-} in the .bib file to indicate an optional
hyphenation point.
Paul
Thanks, Axel and Paul. Inserting just ~ did not work, {\~}worked in this
case:
Trans{\-}lation-independent circadian control of the cell cycle in a
unicellular photosynthetic eukaryote
Miyagishima, Shin-ya et al. (2014). “*Trans-**
** lation*-independent circadian control of
the cell cycle in a unicellular photosyn-
thetic eukaryote.” In: Nature communi-
cations 5, p. 3807.
but not here
A transcriptionally and functionally distinct PD-1,
{\-}javax.xml.bind.JAXBElement{\-}@7a062e7f, CD8,{\-}
javax.xml.bind.JAXBElement{\-}@2110cbd6, T cell pool with predictive
potential in non-small-cell lung cancer treated with PD-1 blockade.
Thommen, Daniela S. et al. (2018). “A tran-
scriptionally and functionally distinct
*PD-1, javax.xml.bind.JAXBElement@7a062e7f,**
** CD8, javax.xml.bind.JAXBElement@2110cbd6,*
T cell pool with predictive potential in
non-small-cell lung cancer treated with
PD-1 blockade.” In: Nature medicine 24,
pp. 994–1004.
Wang, Yaping et al. (2017). “Upregula-
tion of circadian gene ’hClock’ contribu-
tion to metastasis of colorectal cancer.”
In: International journal of oncology 50,
pp. 2191–2199.
I can live with it, since this citation happens to be in the right
column and is still readable.
Wolfgang
