speedata/publisher

This is about the speedata Publisher. Room language is English (and perhaps German)

ViWaldi

@ViWaldi

@pgundlach Habe jetzt mit dem Ouput-Befehl experimentiert, der mir die Daten über mehrere Seiten ausgibt, aber da kann ich z.B. kein Rahmen ziehen oder Daten vertikal ausrichten usw. Hast du noch andere Vorschläge, wie man solche Daten ausgeben kann?

Patrick Gundlach

@pgundlach

@ViWaldi Ich kenne die genauen Umstände nicht. Mit ein wenig Glück kann man sich die Positionen merken (wo fange ich an, wo höre ich auf) und bei AtPageShipout die Rahmen zeichnen. Aber das kommt auf die Umstände an.

ViWaldi

@ViWaldi

@pgundlach Der Hintergrund ist, dass unsere Kunden Rechnungen, Lieferscheine, Aufträge etc. beim Positionstext manchmal mehrere Seiten Text eingeben. Und genau da fällt es mir jetzt auf die Füsse. Es wäre cool, wenn man bei der Zeilendefinition Trein Attribut eingeben könnte, dass die Zeile umgebrochen werden kann.

neolithos

@neolithos

Wir sind unter 03521 8230130 erreichbar. https://tecware-gmbh.de/impressum.html

Ca. 12uhr sollte ich erreichbar sein.

iclukas

@iclukas

Reminder ;)

I just noticed that it’s possible to use negative numbers with substring(). Though not XPath-compatible, I think this should be noted in the docs.

Patrick Gundlach

@pgundlach

@iclukas I will document this

iclukas

@iclukas

I’m currently playing around with the circle / ellipse code and am wondering if a circle should be an ellipse if the grid is not square-based

iclukas

@iclukas

I see my mistake. It’s radiusx, so all is fine.

iclukas

@iclukas

Hi again. I’m having trouble using the --extra-xml option. I would like to use it for including extra font definitions. Obviously (from the code) they are appended to the main XML so this won’t work. For now, I append the main XML to --extra-xmland use an empty layout to have full control about inclusion order, but it just doesn’t feel right. What do you think?

Patrick Gundlach

@pgundlach

@iclukas I think you can use them for this purpose. They are (as you have written) read in the order of appearance after the main layout file. But all the global stuff (including the extra layout files) is executed before the data processing starts. So this works for me:

layout.xml

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

  <Record element="data">
    <PlaceObject>
      <Textblock>
        <Paragraph>
          <Value>Hello world</Value>
        </Paragraph>
      </Textblock>
    </PlaceObject>
  </Record>
</Layout>

data.xml:

<data></data>

dejavu.xml:

<Layout
  xmlns="urn:speedata.de:2009/publisher/en">

  <LoadFontfile name="DejaVuSerif" filename="DejaVuSerif.ttf" />
  <LoadFontfile name="DejaVuSerif-Bold" filename="DejaVuSerif-Bold.ttf" />
  <LoadFontfile name="DejaVuSerif-BoldItalic" filename="DejaVuSerif-BoldItalic.ttf" />
  <LoadFontfile name="DejaVuSerif-Italic" filename="DejaVuSerif-Italic.ttf" />


  <DefineFontalias existing="DejaVuSerif" alias="serif"/>
  <DefineFontalias existing="DejaVuSerif-Bold" alias="serif-bold"/>
  <DefineFontalias existing="DejaVuSerif-Italic" alias="serif-italic"/>
  <DefineFontalias existing="DejaVuSerif-BoldItalic" alias="serif-bolditalic"/>

</Layout>

and serif.xml:

<Layout
  xmlns="urn:speedata.de:2009/publisher/en">

  <DefineFontfamily name="text" fontsize="10" leading="12">
    <Regular fontface="serif"/>
    <Bold fontface="serif-bold"/>
    <Italic fontface="serif-italic"/>
    <BoldItalic fontface="serif-bolditalic"/>
  </DefineFontfamily>

</Layout>

and I run sp --extra-xml dejavu.xml --extra-xml serif.xml

(This is split just to demonstrate the order of --extra-xml)

@iclukas Does this solve your problem or do you need something else?

iclukas

@iclukas

I see. The problem is that I’m using <DefineFontfamily> in my layout.xml, so I keep getting “Font instance not defined” errors.

Patrick Gundlach

@pgundlach

Yes, the font families must be defined after <LoadFontfile>. Any suggestion how to solve this? Something like a --prepend-xml or --preload-xml?

iclukas

@iclukas

Yes, that would work. Since this very I could add this option myself if you like

*special

Patrick Gundlach

@pgundlach

Go ahead, if you want to!

iclukas

@iclukas

I think I’m done. LUA works fine, but I'm having trouble building the whole package. I have a Mac but my target is Debian Stretch. I think I’m missing some prerequisites

Do you have a pointer how to set up the whole dev environment?

Patrick Gundlach

@pgundlach

Building the thing got more complicated due to the external library I am using. I will need to write down something.

iclukas

@iclukas

Maybe you can just have a look at my branch.

iclukas

@iclukas

I’m stuck. I managed to create a ZIP whith rake dist but now sp tells me that module 'ffi' is missing. I’m pretty confident my changes to sp.go are fine. Would you like me to create a pull request anyway?

Patrick Gundlach

@pgundlach

Yes please. I’ve not looked into your branch yet

Are you using your own Luatex? You need the 1.04 from the download page if you want to build it yourself

iclukas

@iclukas

It’s 1.07 :) But I don't know what to do with that zip

Patrick Gundlach

@pgundlach

1.07 is good. I’ll update the build instructions in the manual

iclukas

@iclukas

Ok, I got it now. And it works! But yes, please update the build instructions, that was a hard one.

Patrick Gundlach

@pgundlach

@iclukas is online, thanks

iclukas

@iclukas

Awesome! I have another question: using a variable like this doesn’t work: <DefineFontalias existing="{$font}" alias="Font1"/> but this works: <DefineFontalias existing="Font1" alias="{$font}"/>

Patrick Gundlach

@pgundlach

@iclukas It is hard to believe that :-). I have not tried it but the code for existing and alias are the same. Are you really sure that this is the case?

iclukas

@iclukas

I know, that’s why I was wondering. It doesn’t really matter now because I resorted to using the variable inside <DefineFontfamily>

Somehow $font looks empty to sp in <DefineFontalias existing="{$font}" alias="Font1"/>

iclukas

@iclukas

I tested that $font thing again with a clean setup. It works now, so probably I had something else messed up.

Patrick Gundlach

@pgundlach

@iclukas thanks for the feedback, good to know

iclukas

@iclukas

Hm, I just noticed auto complete stopped working in Atom. I even completely reinstalled it, but to no avail. Does it work for you?

Patrick Gundlach

@pgundlach

It works here. I am using version 3.5.2 of language-speedata-publisher and Atom version 1.30.0

iclukas

@iclukas

Same here, just Atom 1.32.2.

Patrick Gundlach

@pgundlach

I'll check (but I assume that I don't have time today)

iclukas

@iclukas

Ok thanks. Just tried again, wiping everything according to https://discuss.atom.io/t/how-to-completely-uninstall-atom-for-mac/9084/42 Same result, no auto complete. speedata format is being recognised though

iclukas

@iclukas

Ok, a little update: I restored an old version of ~/.atom and Atom.app. Now autocomplete is working again. Will try updating again when I have more time.

Martin Fricke

@mrfr_twitter

I also noticed the same mistake. Atom 1.28.2 works..

iclukas

@iclukas

I checked a few Atom versions today. It still works with Atom 1.31.2 but breaks with 1.32.0

Patrick Gundlach

@pgundlach

Thank you very much @iclukas, I will check what has changed with the 1.32.0 as soon as possible.

(BTW: currently working on PDF/X-3)

Patrick Gundlach

@pgundlach

I don't know what is going on in Atom 1.32. I have asked on https://atomio.slack.com/ but there is not much hope.

Patrick Gundlach

@pgundlach

No news for Atom yet. I belive that the underlying package https://atom.io/packages/linter-autocomplete-jing is broken, as other packages based on it don't work either

Patrick Gundlach

@pgundlach

@/all Good news for Atom-users. When you update the linter-autocomplete-jing package, autocompletion and linting works again.

Where communities thrive

People

Repo info

Activity