superscript/subscript minor behavior glitches

Bug #968959 reported by Andrei Arici
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

In version 0.48.3.1 r9886, if no text is selected, subperscript and subscript buttons toggle text to 7.8 and then between 7.8 and 12 points, despite an 40 points text initial size. Things work well if you select text.

I suggest dissabling buttons while there is no text selected or modify behavior - super/subscript text relative to current font size for the next input leaving currently available text intact as right now everything is reduced to 7.8 and untogling will only result in setting it to 12.

Tags: text ui
Revision history for this message
su_v (suv-lp) wrote :

<off-topic>
> (…) toggle text to 7.8 and then between 7.8 and 12 points, despite
> an 40 points text initial 40 points text initial size.

Note: font sizes in Inkscape are px not pt (see tooltip of the font size selector). Request for additional unit selector already filed and tracked elsewhere.
</off-topic>

Revision history for this message
su_v (suv-lp) wrote :

Expected behavior (quoting the manual):
«Superscripts and subscripts can be created by selecting text and clicking on the corresponding icons ( icon , icon ) in the Tool Controls.

The selected text will be shifted up or down and reduced in size. Superscripts and subscripts can be removed by selecting and then clicking on the same icons. Inkscape implements superscripts and subscripts by setting the baseline-shift attribute to either “super” or “sub”, and by setting the font-size attribute to 65%. Inkscape will only recognize a superscript or subscript if the baseline-shift attribute is set in this manner. The font size can be changed after the superscript or subscript is created. The baseline-shift attribute is not supported by all browsers (e.g. Firefox 4). As a workaround, one can manually shift the text vertically.»
<http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Text-Formatting.html#Text-Formatting-SuperSubScripts>

summary: - suberscript/superscript minor behavior glitches
+ superscript/subscript minor behavior glitches
Revision history for this message
Andrei Arici (andreiaici) wrote :

Thanks for the headsup regarding px and points.

However I really don't think the "expected behavior" is a correct behavior.

Suppose I've written something and now I want the next character to be superscripted. I now have 3 options:

1. Click superscript before writing anything - which reduces everything to 7.8 px. - this is plain wrong.

2. Or write that character
 - then select it
- then click superscript
- then deselect it (because if I start typing I overwrite)
- than to my surprise everything is superscript so I have to select text again
- un-superscript it
- deselect it and start typing.

3. Being aware of the faulty behavior we select chars in the middle only.

Suggested behavior: the next chars after clicking superscript ought to be 66 % of the previous character.

If I hit the "B" button (bold) all the text in the text-object turns bold. If I am to hit superscript at some point, I'd say I'd only want the next char to be super. But everything get's shrinked - and not to 65% of the original, but to 65% of 12 px. It's twice faulty.

Revision history for this message
Beluga (buovjaga) wrote :

I got an even weirder result.

Write a character
- then select it
- then click superscript
- then deselect it (I deselected whole text object and reselected it)
- then to my surprise everything is superscript so I have to select text again
- un-superscript it
- now the un-superscripted text is *above* the superscripted text so there are three levels of super duper fun

Win 7 64-bit
Inkscape 0.92pre1_64bit r15044

Changed in inkscape:
status: New → Confirmed
Revision history for this message
Beluga (buovjaga) wrote :

I set this to Confirmed.

Revision history for this message
Nathan Lee (nathan.lee) wrote :

Hi - thanks for reporting this bug, I'm closing this as part of the migration to Inkscape's new
bug tracker on GitLab.

The two issues still occur. They are now being tracked by https://gitlab.com/inkscape/inbox/-/issues/4166 and https://gitlab.com/inkscape/inkscape/-/issues/2098

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report.

Changed in inkscape:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.