NOT A BUG BUT A SUGGESTED ENHANCEMENT. Not able to use "Small Capitals" effect when formatting text in Draw. FONT EFFECTS dropdown list -which is available in Writer- is not included in Draw. Could this be considered to be included in later versions of Draw?
Format -> Character -> Font Effects -> Effects (dropdown list) -> Without, Capitals, Lowercase, Title, Small capitals
Format -> Character -> Font Effects -> (Effects dropdown list not here)
Yeah I think that this should be included and won't be too hard to include. Marking as NEW and making it HIGH priority as the code is already there, just needs to be brought into Draw. Furthermore, it would/should be uniform across all of the software packaged with LO. Thanks for the heads up on this one
Any news on this?
This feature should be added to Draw, not only for obvious consistency reasons, but also for the sake of typographical correctness. There is no reason why presentations should not adhere to typography rules enforced in text documents.
For instance, in French, the speaker's last name (that generally appears on the first slide) would be typeset in small caps.
*** Bug 70696 has been marked as a duplicate of this bug. ***
See Bug 70696 . Also reproducible in Impress, so lets 'generalize' this bug. If someone is working on this bug, I don't think it's that big deal to fix both at once (no 2 separated bug reports/'projects'). If I'm wrong, please feel free to unduplicate it again.
Created attachment 87904 [details]
Effects dropdown menu missing in Calc.
This is also reproducible in Calc.
Steps to reproduce:
1. Type a word in a cell and save it.
2. Select the word either in the Input Line or in the cell itself.
3. From the menu bar, select Format-Character, select the Font Effects tab, and see that the Effects dropdown menu is missing on the left side of the tab window, between the Font Color dropdown menu and the Relief dropdown menu.
*** Bug 85460 has been marked as a duplicate of this bug. ***
*** Bug 70829 has been marked as a duplicate of this bug. ***
Currently the drop down is visible in Impress/Draw and invisible in Calc. To me this is a bug and not an enhancement, as being able to modify a direct formatting or style option like this is mandatory.
Splitting this original bug about font effects missing in impress/draw and calc into the part for impress/draw (as bug 91932) and leaving this specifically for "font effects in calc". Note that excel doesn't (AFAIK) support the case map attribute
Caolán fixed the bug and closed tdf#91932 but not this one. Access to character properties is available from the sidebar and via main menu. And the font effects tab allows all types of font effect.
(In reply to Heiko Tietze from comment #12)
> Caolán fixed the bug and closed tdf#91932 but not this one. Access to
> character properties is available from the sidebar and via main menu. And
> the font effects tab allows all types of font effect.
No, this isn't fixed. The Effects dropdown (i.e. the one with Capitals, Lowercase etc.) is still disabled in Calc. And don't confuse this with the stuff in Format>Text menu. This is completely different thing technically.
(In reply to Maxim Monastirsky from comment #13)
> No, this isn't fixed. The Effects dropdown (i.e. the one with Capitals,
> Lowercase etc.) is still disabled in Calc. And don't confuse this with the
> stuff in Format>Text menu. This is completely different thing technically.
When I go to character properties via sidebar or main menu I can change the font effect to small capitals in Draw (this ticket is Draw, Calc has the field disabled).
Close this bug and open another, or change the component?
(In reply to Heiko Tietze from comment #14)
> this ticket is Draw
You're right. The original report was about Draw, but later (comment 11) it was changed to Calc, but the Component field wasn't changed.
> Close this bug and open another, or change the component?
I think I'll close this one as a duplicate of bug 91932, and open a new clean report for Calc, as the current situation of reusing an originally Draw bug for Calc is just too confusing.
*** This bug has been marked as a duplicate of bug 91932 ***