Inkscape.org
Beyond the Basics Text Flow into Frame
  1. #1
    garnaldi garnaldi @garnaldi

    Am an Inkscape 92.4 user with Windows 10. I have encountered a most interesting and puzzling behavior by Inkscape. I begin by drawing a text box in which I amass a bunch of H's for example. Then I draw a big letter or digit, let's say an O or 0. I do the Object to Path for the O followed by Object Ungroup. I set text size at 14 and baseline spacing at 80. Now I click Text Flow into Frame. Text disappears. I revert to the text tool. Aha! My numbers have been altered automatically by Inkscape. Text size is shown as 52.91 and line spacing as 289.13! I edit those numbers and, as I minimize them, I am surprised to see the H's reappear and grow in the big O as I keep pressing. This phenomenon reoccurs at each trial. Does anyone have experience with this sort of behavior and how to fix it?

  2. #2
    Maren Hachmann Maren Hachmann @Moini

    Not really, I don't have that version anymore. Bugs that are specific to the 0.92.x series probably won't be fixed anymore, either.

    Can you rephrase your question in a way that it becomes easy to understand what the goal of all the operations is?
    That will make it much easier to give you an answer that will actually help you.

    Generally, you could do one of two things:

    - uninstall 0.92.4 and then install 0.92.5, if you depend on a third-party extension that hasn't been updated yet, or on command line scripts that you cannot update for 1.0. Try it there, maybe it's fixed.
    - uninstall 0.92.4 and then install 1.0. This version has completely rewired the way flowed texts work. It might be that the issue does not exist there.

    For specific help, I need to know more about the goal.

  3. #3
    Iomen rum Iomen rum @iomenrum.rt

    This does happed with me too, it's not a bug just go to the preferences, select text and  under test uncheck the box saying "Use SVG2 auto-flowed text" and there you have it.

     

  4. #4
    Maren Hachmann Maren Hachmann @Moini

    It sounds very much like a bug to me... Using a different text type is a workaround, but it's not a fix.