Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal error with HSpace at the beginning of a paragraph #226

Closed
pgundlach opened this issue Mar 14, 2019 · 4 comments
Closed

Fatal error with HSpace at the beginning of a paragraph #226

pgundlach opened this issue Mar 14, 2019 · 4 comments
Assignees
Labels
Milestone

Comments

@pgundlach
Copy link
Member

<Layout xmlns="urn:speedata.de:2009/publisher/en"
  xmlns:sd="urn:speedata:2009/publisher/functions/en"
  version="3.6">

  <Record element="data">
    <PlaceObject>
      <Textblock >
        <Paragraph>
          <HSpace/>
          <Value>txt</Value>
        </Paragraph>
      </Textblock>
    </PlaceObject>
  </Record>
</Layout>

gives Assertion failed: (vlink(o)==cur_p), function ext_try_break, file ../../../texk/web2c/luatexdir/tex/linebreak.w, line 1271. and a fatal error.

@pgundlach pgundlach added the Bug label Mar 14, 2019
@pgundlach pgundlach added this to the Version 3.8 milestone Mar 14, 2019
@pgundlach pgundlach self-assigned this Mar 14, 2019
@poetaman
Copy link

@pgundlach I wonder what all is not permitted in beginning? In my testing (unrelated to speedata*), a disc node (with penalty:50) in the beginning of nodelist fed to tex.linebreak also results in the same error. I reached your page while searching for any information on this same error, and this is the only hit I got.

@pgundlach
Copy link
Member Author

@reportaman I can't tell you more. Someone has found this bug and I tracked it down that the hspace was at the beginning, but that is about all I know....

@poetaman
Copy link

poetaman commented Dec 30, 2020

Sure, I'll write a test program, and post it on tex.SE, or at least first ask that question there :)

@poetaman
Copy link

poetaman commented Dec 30, 2020

@pgundlach Btw, in my case, adding a local_par node in the very beginning (before disc with penalty) resolved this error. I wonder if that's it, and would cover all cases... In that case, its cleaner than having to check the id's and sequences of id's that hit this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants