Attila Kovacs

if you are already using StyleControls look for the TscStyledForm component and "dropdownforms" demo and set your form shape with "SetWindowRgn"

Of course.

I just don't understand why msbuild would ignore the duplicates, but dcc does not. I added 'System' with -NS to dcc32, just like in the Project settings in the IDE where unit scope names are also set. I would expect the same behavior.

Supresses the error? Why?

given this program Project1; {$APPTYPE CONSOLE} {$R *.res} uses Generics.Collections, System.Generics.Collections; begin end. the ide will not complain, possibly msbuild but with "dcc32 -NSSystem Project1.dpr" it's an "Identifier redeclared". Where’s the logic in that?

I told ya I can't imagine how this automated tool should work on this probem, this is a real PITA go get it right.

I'm almost finished (I had some time in the evenings during my trip to Sardinia), and I would suggest making that image an 'Artifact' in your case, that would make the readers completely ignoring it.

Huh? Is the "scaled" property of the form meanwhile true in your legacy app?

Well, it's not that complicated. Imagine, for example, that there's a logo in a document and a screen reader application needs to help someone understand what's on the screen. Without tags, the screen reader will start reading things like 'line, line, path, rectangle, etc.' But if you tag the group of shapes/lines as /S /Figure /T (Logo), then it simply reads 'Logo.' The same principle applies to pretty much everything else in the document. Here is an example from the PAC you linked, after I added the /Figure tag using PDF-XChange: Now, PDFix will try to tag everything, more or less quite well, but the tags won’t have names to be read, and the graphics won’t be grouped correctly, etc. But I did not check PDFix for the details, maybe you can create templates for better results. It's a pretty neat topic, it reminds me of the Lynx, the console text web browser for Linux back in the days.

Well, I really wouldn't like to add a post-processor behind it, it's basically impossible for it to work properly when, say, the company logo is made up of 40 paths and scribbles. Besides, it can't modify a signed PDF anyway. However, in my form designer, I can add accessibility semantics to the elements, like role, display name, language, etc. and with "gdicomment()", I can pass it to Gnostice, which I’ll expand with a processor and a structure-tree generator. I think I’m going to miss the 3-week deadline, but I believe this is the only sensible solution.

I've just tested some documents my app generates, and they are all rated as Taygetos+. Everything has to be compliant in just 3 weeks, great, thank you @Rollo62.

Ah, that's why I've been cursing lately.

I see, looks like I was wrong about 'in the EU', it's actually just in Germany. Here, you can only provide net price plus VAT per line item, which is pretty much only practical for B2B.

Okay, which format do you use there?

You need PEPPOL BIS UBL (XRechnung UBL from the lib above) with Norwegian customization, see: https://github.com/OxalisCommunity/oxalis/tree/master/oxalis-outbound/src/test/resources/EHFInvoice/2.0 and a validator like: https://anskaffelser.dev/service/validator/ (Interesting that there is a B2C implementation in NO, whereas in the EU it's only for B2B, as you can't pass the gross prices, only the net.)