Re: Exporting as PDF (cropped) is not cropping
> On Oct 19, 2018, at 4:09 AM, Daniel wrote: > > On 19/10/2018 11:54, list_em...@icloud.com wrote: >> When I open a new document, type an equation, and export as PDF (cropped), I >> expect to see a PDF file that has zero extra white space around the >> graphical portion of the math. Instead, I see an entire page with the >> equation on the first line. I.e., no cropping. What am I doing wrong? >> LyX 2.3.0 >> Jerry >> > > Works for me on with LyX 2.3.1 on Windows 10. It crops from the equation to > the page number, so the area is quite large but not the whole page. If I set > the page layout page style to empty (via Document > Settings), I get the > formula only. > > (For a short time the full page is shown in the PDF viewer but it is almost > immediately replaced by its cropped version.) > > Daniel > Daniel nailed it for me. I just needed to set the Page Style to plain so that no header-footer decorations and no page numbers appear. If they do appear, the cropping is such that headers-footers and the page number are included. Thanks. Jerry
Re: weird language management
On 10/22/2018 03:38 AM, Pol wrote: Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote: On 10/21/2018 11:48 AM, Paolo M wrote: I have noticed that spellchecker does not work, if an alternative language has been given. Is that a bug? Do you have a vocabulary loaded for the alternative language? Not to my knowledge. So, just how were you imagining that the spellchecker would do its checking, then? How to check? There are many spellcheckers supported by LyX and multiple operating systems to which LyX has been ported, and you haven't told us which you use. I urge you to determine which spellchecker you've installed, by selecting Tools > Preferences > Language Settings > Spellchecker Then use a search engine to find the documentation for that spellchecker, and then read its documentation to learn how to install the vocabulary for whatever languages are relevant to your purposes.
Re: auto fixing mispelled words
On 10/22/2018 04:16 AM, Pol wrote: A possible improvement of the spellchecker facility: Common, typical mispellings made by authors could be istantaneously autocorrected by lyx, by checking a suitable list maintained by authors themseves. If there is to be a list of substring substitutions automatically to be made, then there is no particular reason to confine it to misspellings. If I somehow know that I am always going to intend to have typed “watermelon” when I type “giraffe”, or “\sim” when I type “\defeq”, then I will want these substitutions made as well. But if I know that I never intend to type “satistics” then why would I still do it so often that the ordinary find-and-replace function weren't sufficient to fix the occasional lapse? And do I really want a wordprocessor as if cynically imagined by Cyril M. Kornbluth https://www.gutenberg.org/files/51233/51233-h/51233-h.htm
Re: weird language management
I had that problem the other day. You probably need to install the appropriate spellcheck dictionaries. On Sun, 21 Oct 2018 at 14:49, Paolo M wrote: > I have noticed that spellchecker does not work, if an alternative language > has been given. > Is that a bug? > > paolo m. > -- John Kane Kingston ON Canada
auto fixing mispelled words
A possible improvement of the spellchecker facility: Common, typical mispellings made by authors could be istantaneously autocorrected by lyx, by checking a suitable list maintained by authors themseves. p.
Re: weird language management
Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote: > On 10/21/2018 11:48 AM, Paolo M wrote: >> >> I have noticed that spellchecker does not work, if an alternative >> language has been given. >> Is that a bug? > > Do you have a vocabulary loaded for the alternative language? Not to my knowledge. How to check? thank you
Re: Parentheses keys are reversed in Hebrew
Hi, I've made some more experiments (this time on the git version) and it seems the behavior changes based on how hebrew is typed: * If you are using the system's keyboard layout then () get reversed, and [] {} <> are correct. * If you are using lyx's hebrew keymap (and system's keyboard layout as english) then () are correct and [],{} and <> are reversed. In both cases, the display in lyx matches xelatex output (which is good). Thanks, Guy On Mon, 22 Oct 2018 at 09:52, Guy Rutenberg wrote: > Hi, > I'm re-sending my last message as it appears I accidentally didn't send it > to the list. I've also added the lyx-devel, as it seems to be more > appropriate. > > On Fri, 19 Oct 2018 at 17:22, Guy Rutenberg > wrote: > >> On Fri, 19 Oct 2018 at 11:05, Daniel wrote: >> >>> >>> However, this is with an English, German, etc. keyboard layout. This >>> changes if I switch to the Hebrew keyboard layout. But then the Hebrew >>> keyboard layout seems to have parenthesis switched relative to the >>> English: >>> >> >> I'm referring to the case of using Hebrew keyboard layout. >> >>> >>> >>> https://en.wikipedia.org/wiki/Hebrew_keyboard#/media/File:Hebrew_keyboard_layout.png >>> >>> >> I don't know how made that diagram, but I'm pretty sure that he didn't >> use an actual Hebrew keyboard. I have around seven different keyboards >> around me right now from different manufacturers, non have this weird >> things with reversed parenthesis. Even the actual keyboard photo in the >> Wiki article shows the parenthesis to be normal and not reversed as in the >> diagram. >> >> >>> So, if you are using a Hebrew keyboard layout, then LyX seems to behave >>> correctly. But in that case I am wondering why other applications don't >>> behave that way for you. >> >> >> Because LyX behavior is unexpected to the normal user. >> >> On Fri, 19 Oct 2018 at 13:11, Jürgen Spitzmüller wrote: >> >>> >>> >>> Please comment here: >>> https://www.lyx.org/trac/ticket/11191 >>> >>> We generally need to audit LyX's behavior with bracket/parens input in >>> RTL, but we urgently need input from experienced users. >>> >>> >> I've added a new comment there as well. I'll gladly help to fix this >> issue if someone can point me in the right direction. >> > > > I've looked again at the bug and the patch linked there. It seems that the > code handling parenthesis had been moved to somewhere else. Where does it > resides now? I want to try and patch it so it won't reverse parenthesis in > hebrew. > > Thanks, > Guy >
Re: Parentheses keys are reversed in Hebrew
Hi, I'm re-sending my last message as it appears I accidentally didn't send it to the list. I've also added the lyx-devel, as it seems to be more appropriate. On Fri, 19 Oct 2018 at 17:22, Guy Rutenberg wrote: > On Fri, 19 Oct 2018 at 11:05, Daniel wrote: > >> >> However, this is with an English, German, etc. keyboard layout. This >> changes if I switch to the Hebrew keyboard layout. But then the Hebrew >> keyboard layout seems to have parenthesis switched relative to the >> English: >> > > I'm referring to the case of using Hebrew keyboard layout. > >> >> >> https://en.wikipedia.org/wiki/Hebrew_keyboard#/media/File:Hebrew_keyboard_layout.png >> >> > I don't know how made that diagram, but I'm pretty sure that he didn't use > an actual Hebrew keyboard. I have around seven different keyboards around > me right now from different manufacturers, non have this weird things with > reversed parenthesis. Even the actual keyboard photo in the Wiki article > shows the parenthesis to be normal and not reversed as in the diagram. > > >> So, if you are using a Hebrew keyboard layout, then LyX seems to behave >> correctly. But in that case I am wondering why other applications don't >> behave that way for you. > > > Because LyX behavior is unexpected to the normal user. > > On Fri, 19 Oct 2018 at 13:11, Jürgen Spitzmüller wrote: > >> >> >> Please comment here: >> https://www.lyx.org/trac/ticket/11191 >> >> We generally need to audit LyX's behavior with bracket/parens input in >> RTL, but we urgently need input from experienced users. >> >> > I've added a new comment there as well. I'll gladly help to fix this issue > if someone can point me in the right direction. > I've looked again at the bug and the patch linked there. It seems that the code handling parenthesis had been moved to somewhere else. Where does it resides now? I want to try and patch it so it won't reverse parenthesis in hebrew. Thanks, Guy