Description: hello, sorry for being so persistent :) or rather, thank you for your patience and openness so far :) in short: I think it is a mistake to identify an EM-ed text as "italic"-ed.. that is, to indicate "A as italic" ON, when "EM" is applied... the good practice (I think) would be to indicate "Em" ON only.. it is, sure, logical if you approach it from the text's appearance :) that is, when it looks italic, to identify it as "italic"-ed ... but this seems to be a mistake on the longer run... not to mention that introducing styles at the character level demands the understanding of the difference between DF and S... okay, just look at the 3 steps... PLZ 2 A and 2 B are "forks", alternate steps :) thank you! (and sorry if I again misunderstood something) Steps to Reproduce: STEP #1.: select a few words and apply "Em" ____ 2/A. now, click on "clear direct formatting" (nothing happens) ____ 2/B. now click "italic" (A) in DF toolbar... 3(B). then click "clear DF"... Actual Results: @ STEP #1.: "Em" button goes ON, "A as italic" (in DF toolbar) is ON, too... @ step 2/A: nothing happens -- illogical, in my HO, cause DF is indicated to have been applied... so we should be able to clear it using "clear DF"... BUT, at the same time, it is absolutely logical, cause NO DF has been applied @ step 2/B: users are used to "undo" DF by clicking its icon again... so, chances are that someone will click "A as Italic".. to make the italic disappear... AND it will !!!!!! :) now we have "Em" ON, "A as italic" OFF, and the text looks NON-italic... (illogical, cause "Em" is ON) @ step 3 (B): once "clear DF" is applied, the text gets italic again, "A as italic" is ON, "Em" is ON, and the text looks "italic" (it is emphasized) ... WE are back at step #1 (which is actually LOGICAL if you have STYLES toolbar ON... and you see that EM is ON... but not logical in terms of indicating DF ON when there is no DF) Expected Results: @ 2/A: since DF is indicated (to have been applied), clicking "clear DF" should clear it -- no, not the text... but the indication :) "A as italic" should be OFF @ 2/B: the same thing should happen as when clicking the "clear DF", it should clear DF.. including the indication (this is what happens) ... BUT, at the same time, since EM is ON, the text should look like "italic" (=emphasized) @ 3 (B): when "clear DF" is issued, DF buttons should be set to OFF... (in any circumstances) including that the opposite should never happen :) here, at step 3(B), since no DF was indicated previously, NOTHING should happen.. - - - - the point: STEP #1: when EM is clicked or have been applied otherwise, "Em" should be ON... but "A as italic" in DF toolbar should NOT be ON... (unless it is clicked, but that's a jammed usage, so let's stick to a clean case: when Em is applied, "A as italic" in DF toolbar should NOT be ON, it should remain as it was... if the behavior @ STEP #1 was modified, no illogical situations would come about at the further steps... ( -- clicking the "clear DF" woulds do nothing, but no DF would be indicated either; -- then clicking "A as italic" would result in the active state of "A as italic" (ON)... both EM and "A as italic" would be ON... -- clicking "clear DF" (step 3(B) would clear "A as italic", but not Em, that is, "EM" would be ON, and the text would look still "italic" = emphasized .. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Hello, how to apply Em? STEP #1.: select a few words and apply "Em"
(In reply to raal from comment #1) > Hello, how to apply Em? > STEP #1.: select a few words and apply "Em" Yes it is unclear as to the OPs usage. Using <Ctrl>+I applies Direct Formatting, as does the Italic button from the Formatting toolbar. Only by enabling the Formatting (Styles) toolbar, is the "E" button action applying the "Emphasis" style to the selected text span. Again--"Em" is not a LibreOffice command, we deal with XML manipulation of ODF. OP seems to be expecting some mix HTML5/CSS3 concepts which we do not support directly--ONLY via our XHTML export process.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20190321
Dear peter josvai, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp