Re: pasted non-acceptable symbol

Le 05/12/2016 à 09:50, Jean-Marc Lasgouttes a écrit : Le 10/11/2016 à 10:19, Jean-Marc Lasgouttes a écrit : So shall I apply it? Yes, please. Done in master at 6dfbab31. Richard, this is candidate for branch too, since it leads to crashes. Ping :) Richard, is this OK for branch? Ping Pin

Re: pasted non-acceptable symbol

Le 10/11/2016 à 10:19, Jean-Marc Lasgouttes a écrit : So shall I apply it? Yes, please. Done in master at 6dfbab31. Richard, this is candidate for branch too, since it leads to crashes. Ping :) Richard, is this OK for branch? JMarc

Re: pasted non-acceptable symbol

Le 10/11/2016 à 10:19, Jean-Marc Lasgouttes a écrit : Le 09/11/2016 à 21:45, Stephan Witt a écrit : Am 09.11.2016 um 12:10 schrieb Jean-Marc Lasgouttes : Le 08/11/2016 à 14:56, Stephan Witt a écrit : I tested your patch and it works for me. The change of "lib/unicodesymbols“ leads to proper o

Re: pasted non-acceptable symbol

Le 09/11/2016 à 21:45, Stephan Witt a écrit : Am 09.11.2016 um 12:10 schrieb Jean-Marc Lasgouttes : Le 08/11/2016 à 14:56, Stephan Witt a écrit : I tested your patch and it works for me. The change of "lib/unicodesymbols“ leads to proper output. I cannot tell how the impact of the latter chang

Re: pasted non-acceptable symbol

Am 09.11.2016 um 12:10 schrieb Jean-Marc Lasgouttes : > > Le 08/11/2016 à 14:56, Stephan Witt a écrit : >> I tested your patch and it works for me. The change of "lib/unicodesymbols“ >> leads to proper output. I cannot tell how the impact of the latter change is. > > So shall I apply it? Yes, pl

Re: pasted non-acceptable symbol

Le 08/11/2016 à 14:56, Stephan Witt a écrit : I tested your patch and it works for me. The change of "lib/unicodesymbols“ leads to proper output. I cannot tell how the impact of the latter change is. So shall I apply it? I prefer to leave the rest in the hands of somebody who knows what this i

Re: pasted non-acceptable symbol

Am 08.11.2016 um 21:03 schrieb Enrico Forestieri : > > On Tue, Nov 08, 2016 at 02:28:51PM +0100, Stephan Witt wrote: >> Am 07.11.2016 um 15:34 schrieb Enrico Forestieri : >>> >>> On Mon, Nov 07, 2016 at 01:31:31PM +, Guenter Milde wrote: As the meaning of LINE SEPARATOR and PARAGRA

Re: pasted non-acceptable symbol

On Tue, Nov 08, 2016 at 02:28:51PM +0100, Stephan Witt wrote: > Am 07.11.2016 um 15:34 schrieb Enrico Forestieri : > > > > On Mon, Nov 07, 2016 at 01:31:31PM +, Guenter Milde wrote: > >> > >> As the meaning of LINE SEPARATOR and PARAGRAPH SEPARATOR is clear from > >> http://unicode.org/versio

Re: pasted non-acceptable symbol

Am 07.11.2016 um 10:59 schrieb Jean-Marc Lasgouttes : > > Le 06/11/2016 à 14:30, Jean-Marc Lasgouttes a écrit : >> This is a more radical approach that what I have in mind, and I do not >> know whether it is safe. My idea was to modify the Row building code and >> replace the character with some v

Re: pasted non-acceptable symbol

Am 07.11.2016 um 15:34 schrieb Enrico Forestieri : > > On Mon, Nov 07, 2016 at 01:31:31PM +, Guenter Milde wrote: >> >> As the meaning of LINE SEPARATOR and PARAGRAPH SEPARATOR is clear from >> http://unicode.org/versions/Unicode5.2.0/ch05.pdf >> we can transform them to the corresponding LaT

Re: pasted non-acceptable symbol

On 2016-11-07, Jean-Marc Lasgouttes wrote: > Le 07/11/2016 à 14:31, Guenter Milde a écrit : ... > Converting them is possible in insertStringAsXXX and in tex2lyx, as I > wrote. But we cannot forbid the characters to be in our documents (or if > we can, it will be a waste of energy to catter for

Re: pasted non-acceptable symbol

Le 07/11/2016 à 14:31, Guenter Milde a écrit : Finally, I convinced myself that your approach is correct if we want to keep the breaks. In the following patch I add some one screen hints of what is going on. I could use a color of the characters, but I am not sure what to do, these are actual cha

Re: pasted non-acceptable symbol

On Mon, Nov 07, 2016 at 01:31:31PM +, Guenter Milde wrote: > > As the meaning of LINE SEPARATOR and PARAGRAPH SEPARATOR is clear from > http://unicode.org/versions/Unicode5.2.0/ch05.pdf > we can transform them to the corresponding LaTeX representation: > > 0x2028 "" "

Re: pasted non-acceptable symbol

On 2016-11-07, Jean-Marc Lasgouttes wrote: > Le 06/11/2016 à 14:30, Jean-Marc Lasgouttes a écrit : >> This is a more radical approach that what I have in mind, and I do not >> know whether it is safe. My idea was to modify the Row building code and >> replace the character with some visual cue (in

Re: pasted non-acceptable symbol

Le 06/11/2016 à 14:30, Jean-Marc Lasgouttes a écrit : This is a more radical approach that what I have in mind, and I do not know whether it is safe. My idea was to modify the Row building code and replace the character with some visual cue (in addition with the row breaking), because I am not co

Re: pasted non-acceptable symbol

Am 06.11.2016 um 14:30 schrieb Jean-Marc Lasgouttes : > > Le 05/11/2016 à 21:25, Stephan Witt a écrit : >>> 4/ catch the characters at the level of the row breaking algorithm >>> (TextMetrics::breakRow). This should be pretty straightforward to do. >> >> Yes, this would be the best solution. It

Re: pasted non-acceptable symbol

Le 05/11/2016 à 21:25, Stephan Witt a écrit : 4/ catch the characters at the level of the row breaking algorithm (TextMetrics::breakRow). This should be pretty straightforward to do. Yes, this would be the best solution. It seems so easy that I tried to come up with a patch myself. See attache

Re: pasted non-acceptable symbol

Le 06/11/2016 à 13:25, Stephan Witt a écrit : After doing some code analysis and thinking again I came to the conclusion that my patch is not the best one. One shouldn’t handle U+2028 and U+2029 the same way. To treat LINE SEPARATOR as a new line is ok, IMO. The PARAGRAPH SEPARATOR needs a differ

Re: pasted non-acceptable symbol

Am 05.11.2016 um 21:25 schrieb Stephan Witt : > > Am 05.11.2016 um 16:31 schrieb Jean-Marc Lasgouttes : >> >> Le 05/11/2016 à 13:30, Jean-Marc Lasgouttes a écrit : >>> OK, I can reproduce it now. The problem is with characters >>> LINE SEPARATOR (U+2028) >>> PARAGRAPH SEPARATOR (U+2029) >>> >>>

Re: pasted non-acceptable symbol

Le 05/11/2016 à 13:30, Jean-Marc Lasgouttes a écrit : OK, I can reproduce it now. The problem is with characters LINE SEPARATOR (U+2028) PARAGRAPH SEPARATOR (U+2029) Since they break line/character in string display, we get "interesting" consequences when trying to move cursor. It should not

Re: pasted non-acceptable symbol

Le 04/11/2016 à 21:08, Stephan Witt a écrit : I tried to preview the example file Maksim sent to the list (I’ll attach it again). Without the patch the crash happens when LyX is trying to highlight the error location in the document - the line containing the offending illegal character \u2028.

Re: pasted non-acceptable symbol

Le 04/11/2016 à 11:58, Stephan Witt a écrit : JMarc, are you able to make sense of the following facts? Could you try with the patch at http://www.lyx.org/trac/ticket/10443 ? I’ve use git update instead and now I’m at d207e85cfda2893de4e6c7f419c58aa342395f47. But - no, the crash is not gone

Re: pasted non-acceptable symbol

Le 04/11/2016 à 11:58, Stephan Witt a écrit : I’ve use git update instead and now I’m at d207e85cfda2893de4e6c7f419c58aa342395f47. But - no, the crash is not gone. I’ve attached a slightly improved version of my patch. Obviously, this is a work-around only, I know. I guess it is Qt5 only, si

Re: pasted non-acceptable symbol

Am 04.11.2016 um 10:48 schrieb Jean-Marc Lasgouttes : > > Le 03/11/2016 à 22:06, Stephan Witt a écrit : >> Hi Maksim, >> >> thank you for sending the example. I can reproduce the crash in the debugger >> with LyX 2.3.x master. >> >> JMarc, are you able to make sense of the following facts? > >

Re: pasted non-acceptable symbol

Le 03/11/2016 à 22:06, Stephan Witt a écrit : Hi Maksim, thank you for sending the example. I can reproduce the crash in the debugger with LyX 2.3.x master. JMarc, are you able to make sense of the following facts? Could you try with the patch at http://www.lyx.org/trac/ticket/10443 ? JMarc

Re: pasted non-acceptable symbol

Am 01.11.2016 um 18:04 schrieb Maksim Isakin : > > > Hi Stephan, > > Thanks for your response. The document is attached. > > Maksim. > > Hi Maksim, thank you for sending the example. I can reproduce the crash in the debugger with LyX 2.3.x master. JMarc, are you able to make sense of the

Re: pasted non-acceptable symbol

On 01.11.2016 19:37, Maksim Isakin wrote: >> On Nov 1, 2016, at 2:27 PM, racoon > > wrote: >> >> On 01.11.2016 18:04, Maksim Isakin wrote: >>> Thanks for your response. The document is attached. >> >> Hi Maksim, >> >> The problem seems to be a number of LS (line separator?)

Re: pasted non-acceptable symbol

On 01.11.2016 18:04, Maksim Isakin wrote: Thanks for your response. The document is attached. Hi Maksim, The problem seems to be a number of LS (line separator?) characters. I opened your file with Notepad++ which made them visible. Then did a search and replace and the error was gone. I g

Re: pasted non-acceptable symbol

Hi Stephan, Thanks for your response. The document is attached. Maksim. Lecture6.lyx Description: Binary data > On Oct 31, 2016, at 9:05 PM, Stephan Witt wrote: > > Am 31.10.2016 um 18:13 schrieb Maksim Isakin : >> >> Hello, >> >> There is a bug arising from a non-acceptable symbol (the

Re: pasted non-acceptable symbol

Hi Stephan: You are right. These are hard to find. I have been in this several times in last semester. I'm eager to see what the LyX developers say, but here are tricks I've learned. I bet one Euro we are talking either about "smart quotes" (angled " or ') . This happens a lot if I copy out of

Re: pasted non-acceptable symbol

Am 31.10.2016 um 18:13 schrieb Maksim Isakin : > > Hello, > > There is a bug arising from a non-acceptable symbol (the text is copy-pasted > from another document). I cannot find the symbol because it is not displayed. > I couldn’t find an option to filter these symbols out either. The report i

pasted non-acceptable symbol

Hello, There is a bug arising from a non-acceptable symbol (the text is copy-pasted from another document). I cannot find the symbol because it is not displayed. I couldn’t find an option to filter these symbols out either. The report is below. Thanks, Maksim Isakin ( 1) 1 lyx 0x000105aa