https://bugs.kde.org/show_bug.cgi?id=391796
David REVOY <i...@davidrevoy.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i...@davidrevoy.com
--- Comment #6 from David REVOY <i...@davidrevoy.com> ---
Hi! I'm reading this thread late (unfortunately) and I find here a big *big*
misunderstanding:
> "when we discussed this with Deevad, he said that for comic balloons, people
> would use manual linebreaks anyway, instead of automatic wrapping."
@boud: I said that in the context of my usage at that time and in a technical
way regarding SVG; because SVG had too many issue to support flowed text with
automatic wrapping. I can't imagine I say that in the context of
authoring/creation of text! SVG made so many issues on my side that I was
forced to use manual line-breaks and I still use that since that time. It's not
a choice; it's a pain, a workflow bottleneck that slows me and just a
workaround that I embraced among many other to make Pepper&Carrot a reality.
For more details about the issue, flowed text caused problems for Pepper&Carrot
translation system around episode 13 because I had only flowed text with the
Inkscape custom SVG implementation for it (the one here by default when you
create a text) and all my SVGs had issues with other SVG readers and also
caused issue when text was overflowing, with missing texts or objects not
visible at all.... I realised at that time two SVGs families were existing:
"Inkscape SVG" and W3C SVG". I spent days into converting line-breaks over
dozen of episodes with dozen of pages in dozen of languages; that was weeks of
point-and-click fix one by one files.
Automatic wrapping is very useful for prototyping dialogues. During the
creation of a comic, when a dialog or a good line for a character suddently
cross mind and a balloon needs to be tweaked it's better to just blindly type
and not care about the ideal line-break pattern. It's quick to get things done
and also helps comic artist at defining "a spatial budget" in the panel prior
writing something. Adapting line-break manually later for graphical reason is
always possible, even in a flowed text box.
So, please consider automatic wrapping as something really high on my
wish-list. I was searching for it this evening on the bug-tracker because I was
wondering why this thread has been sleeping for so long. I thought this feature
was part of the text-tool re-design from scratch and reading here that I'm
attributed (and so, responsible) for slowing down any progress on it made me
very sad because I'm waiting for that feature specifically since the refactor
of the text-tool and I agree with all feedback of Tyson here.
--
You are receiving this mail because:
You are watching all bug changes.
