[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #11 from Regina Henschel--- Heiko: I see it different. Perhaps the problem is clearer, if I describe it with markup, although that is not the internal representation: The text has the form R G B Now I select the G and press key g. Expected: G has been replaced with g R g B But I get R g B It seems, that LO does a "delete" followed by an "insert" instead of a true "replace". For an "insert" it is the correct behavior to continue the style of the previous character, but here a "replace" is intended and the undo names it "Replace". To get what you want, you have to insert the g after the G and then go back and delete the G. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #10 from Heiko Tietze--- If you have a whitespace between the characters you can change the font being entered. The same is true for selections. But anyway, I believe there are good reasons to keep the formatting as it is. The continuation of formatting until a whitespace character is more convenient as the rare cases when properties are changed arbitrarily. Of course, I might be wrong. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #9 from Kevin--- Created attachment 133410 --> https://bugs.documentfoundation.org/attachment.cgi?id=133410=edit steps for alternate aspect of bug described in comment -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #8 from Kevin--- This has another manifestation - simply changing the font (or format) affects characters not even selected - see new attachment107857.ods. 1. insert blinking cursor between "I" and "N" in cell B3 (don't select any characters, just put the cursor in that position) 2. set the font to Symbol, planning to type the U+2665 necessary to get the heart result: see D3 – simply change the font without typing anything automatically changes the font for the existing characters! to reproduce without the ods file: 1. set the font to arial 2. type two characters 3. position the cursor between the characters 4. change font to symbol 5. the whole cell changes to symbol on its own (the user desires to type new characters in symbol font -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 Thomas Lendochanged: What|Removed |Added Blocks||102946 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102946 [Bug 102946] [META] Styles bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #7 from Heiko Tietze--- (In reply to Regina Henschel from comment #6) > Your screencast does not contain the critical part. Mark the green G and > enter a g. Ah... on editing it takes the style from the character before. Make me *bold*. Make me *b * (continuation the style is not questionable) Make *me* bold. (entering text after the e keeps the bold style) Make *me *bold. (entering text before the b keeps the bold style) Make *me* bold. (entering text before the b has no bold style) Doing the same with colors it works similarly: RedR RGreenG GBlue (Font color set to red/green/blue until the next word, ie. including the character. R=Entered text is red, G=Green.) Same is true for LibO and Office2010 -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #6 from Regina Henschel--- Your screencast does not contain the critical part. Mark the green G and enter a g. Expected: You get a green g. Currently: You get a red g. Another hint (besides the empty element), that this is really a bug: Do the same with RGB without spaces. Now you get a green g. The same error is in Writer. The behavior is different from MS Office and WordPad, SoftMaker and KingSoft Writer. Gnumeric gives a red g. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #5 from Heiko Tietze--- Created attachment 133373 --> https://bugs.documentfoundation.org/attachment.cgi?id=133373=edit Screencast I don't get the issue, see my screencast. In general, we keep the style from the previous part for good reasons. Lets say want you enter a statement in bold, then you switch bold on first and enter the text later. If you do the same afterwards with a selection it makes of course no sense to keep bold active. The same is true for other style elements such as font color. Is that really different from other tools? -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 Regina Henschelchanged: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #4 from Regina Henschel --- I think it is a bug, because it leaves over an empty span element. If it was an intended behavior, the empty span element would have been removed. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 107857] Incorrect Formatting Logic
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 Thomas Lendochanged: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #3 from Thomas Lendo --- Add keyword needsUXEval, maybe it's an intended behavior. But I also stumbled over this issue in Writer in the past. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise