Re: [Inkscape-devel] Text improvements

14 Nov 2016

      Hi again.
First of all Text tool has a option in prefs to set to last used style
:), I dont know it, sorry for the noise.
Second I find a bug in 0.92.x and trunk with unitless line heights. The
problem is:
Select unitless value, for example 1.0, start typyng and units become
10000% also on return the text go very far away making unitless
unusable currently in my computer.
Cheers, Jabier.
On Sun, 2016-11-13 at 22:36 +0100, Jabiertxo Arraiza Cenoz wrote:
...
Maybe we can set default line height to unitless in prefs at close
inkscape?
On Sun, 2016-11-13 at 21:30 +0000, C R wrote:
...
In fact, I'd go as far as to say that if the user sets the units to
anything other than em or unitless, the spacing should probably
stay
the same... (as it does now). I mean explicitly setting the line
height for something to mm for example, it might be useful to keep
that line height no matter what the font size is. So say you're
trying
to get your flowed text to line up over a set of lines that are
20px
apart. Setting the units to px, and changing the value to 20 would
allow you to experiment with the font size without changing the
baseline of the font (and thus keeping the letters all nice and
lined
up on those lines. The user can always switch to em or unitless
(which
I think is a useful default for most people), and changed in the
special cases that need fixed line spacing of a particular measure.
In short:
Case 1 (Default): Unit set to unitless (I don't care what the exact
measurement is, I just want it to look good, and be able to have
the
line spacing adjust with the font size)
Case 2 (User changes): Units set to a specific unit of measurement
(mm, px, etc) - (I care what the units are because I've set them to
something, and I want you to preserve the line height I set,
because
it's a fixed height, not based off font size)
So both use cases are handled.
-C
On Sun, Nov 13, 2016 at 9:18 PM, C R <cajhne@...400...> wrote:
...
...
"em" is NOT what you want if you want the line spacing to
increase as
you change font size. If you use 'em' or any other unit, the
line
spacing is fixed to that value (unless you explicitly override
it).
em in css is supposed to provide a size relative to the font-
size...
no? I mean that's what I use it for...
So 1em on a 20px font is 20px
therefore:
if I change a 20px font to 30px, 1em = 30px
if I change it to 180px, 1em = 180px
Sure, it's still just 1em (a fixed value), but what it translates
to
in terms of px, mm, in, etc is in relation to the font size...
Am I wrong? :)
...
What you want to use is a unit-less value.
        https://developer.mozilla.org/en-US/docs/Web/CSS/line-h
ei
ght
Okay, so the REAL problem is inheritance conflicts associated
with
em.
That's fine with me, then let's use unitless values instead.
According to the links posted, under normal circumstances it does
the
same thing as em (acts as a multiplier to the font-size), but is
not
affected by inheritance. Fine with me. :)
-C
...
...
On Sun, 2016-11-13 at 14:43 +0000, C R wrote:
...
1.- Remove set default text format definition whith only
click.
Is hard to use well, give usualy bad results and most
important
text
default styling is changed magicaly to the final user. I
know
it
and
be
brong on tenxt editing several times in the same doc.
2.- Line height changes not work correctly if there is
selected
text,
is hard to change baseline once the text is entered, finaly
I
become
coping the text and pasting into a new text item
3.- If you change the size of a text, baseline is not
updated
and
also
become to "bug" 2
Okay, I work with a lot of text all the time. I've kinda
accepted
that
it's a pain in the ass compared to a lot of other programs
I've
used
in the past in a few ways, some of them highlighted by
Jabier.
Here are my recommended fixes based on my own text-heavy
workflows:

Get rid of all concepts of a "default font", and replace

with
"last
used". Most often you just want to use the last font you
were
using
before. It's much easier than trying to define a universal
default,
forgetting what the default you set is, and having to
change
a
bunch
of things around after you see it.

Replace that value with the value of the the last font

used.

Fix ctrl+shift+v to paste the style correctly when a

flowed text
box is selected, and make it possible to paste style
between
flowed
and non-flowed text. (It's current broken).

Use "em" as the default units for spacing between

baselines: em
is
based on the height of the font, and therefore provides a
vector-
like
scaling of spaces between lines during font-size resizing-
thus if
you
change the font-size, you can be sure the line-spacing is
going to
be
the same visual spacing that you just painstakingly
adjusted
to fit
the chosen font. The increment should be changed to a
fractional
amount of em (0.05) for proper granularity (though 0.1
increment
would
be okay for most purposes, imho) 1 em is too much of an
increment.
If you do these things these problems *should* vanish, and
you can
remove that button from the text properties, and users can
just
copy/paste styles from headlines, paragraphs, etc, etc.
without
having
to worry about default fonts.
The only exception to this is of course if Inkscape stores
a
default
font value for the document. In which case, keep the button
and
load
the default font only when the document is opened. This
will
provide
the benefit of a default staring font, without requiring
the
user
to
continually sumble over it for the rest of the editing
session.
If anyone wants to see workflow diagrams on these points
let
me
know.
Thanks for your work on this, Jabier!
-C
On Fri, Nov 11, 2016 at 2:39 PM, Jabier Arraiza
<jabier.arraiza@...2893...> wrote:
> 
> Hi Sylvain.
> Reply inline
> > 
> > (1) When you click on the document with the text tool,
> > and
> > change
> > text
> > format before typing anything, default text format is
> > changed
> > accordingly. It shouldn’t.
> > 
> > But I’m testing the feature: if you change the format
> > before
> > typing,
> > you
> > can’t type anymore, you have to click again on the
> > document,
> > means
> > creating a new text object. So the fix should be:
> > 
> > (1) If you change text format in the control bar with
> > the
> > text
> > tool
> > and
> > no text object focused, it should only apply to the
> > next
> > text
> > creation
> > and should not be set as the default text format.
> 
> YES!
> 
> 
> > 
> > 
> > (2) Line height should only be changed for full lines:
> > the
> > control
> > should be disabled/grayed when characters are selected.
> 
> Not, I think is best always working the same has or not
> has
> selected
> glyps and the changes apply to the whole text always.
> 
> > 
> > (3) The baseline (I guess ‘vertical shift’) should be
> > updated
> > proportionally with text size changes.
> 
> Sure for % line heights, not sure about the others.
> 
> > 
> > I can’t test (3), my controls (kerning, shift and
> > rotation) are
> > keeping
> > disabled when text is focused, I don’t understand why.
> 
> All the best, Jabier.
> 
> 
> ---------------------------------------------------------
> --------
> -------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer
> platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-dev
> el

Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel