On Sat, Mar 18, 2017 at 03:41:20PM +0000, Guenter Milde wrote: > On 2017-03-18, Enrico Forestieri wrote: > > On Sat, Mar 18, 2017 at 03:06:09PM +0100, Guillaume Munch wrote: > > ... > > >> > I think we have to make do with the ugly zero-space inset. > > >> Or special/invisible unicode characters could be made visible by changing > >> the character before painting. > > > However, this is going to be an issue only when exporting a document > > to previous versions and editing it with that version. So, future > > possible workarounds are not going to help. > > > It would not be an issue if that character could be searched for, but > > this is not possible either. > > How did you test this? > I could find a text with ZWSP, if I inserted the ZWSP into the search box > from Insert>Special Char>Symbols.
I mean when searching for a single ZWSP. The "simple" search does not work because the find next button is not activated, while the "advanced" search works only when deselecting "ignore format" and placing an empty ERT just after the ZWSP. Even if in this case the ZWSP is actually found, nothing is selected, so that you don't have any visual clue. The way you insert a ZWSP is irrelevant (I used unicode-insert 0x200b). > OTOH, copying text with ZWSP from a text editor into LyX failed as well as > copying text with ZWSP form LyX's buffer window into the search box. BUt copy/paste of a single ZWSP works in LyX. Even if you don't see anything highlighted, the scissors and the copy icons get activated. So, you could copy the word just after an em-dash without realizing that you are also copying a ZWSP. > > And even fixing this is not going to help > > with previous lyx versions. > > True. Therefore, also the "Special character allowbreak" patch will not help > here. It would, however help with documents transformed from 2.1 to 2.3. In fact, the issue here is exporting to previous formats and editing with the corresponding lyx version. If this is deemed a minor glitch, I will be happy to use the ZWSP. -- Enrico
