Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Graeme Geldenhuys
On 22/03/2019 17:04, Martok wrote: > Especially for tiny teams, the decision of spending 6k€ or hiring a new > developer to maintain the toolchain is, sadly, a no-brainer. I developed fpGUI before I started working at that company. Same with tiOPF, not initially developed by me, but existed

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Martok
> Tell them how much money (£2000+) they save per developer by using FPC > versus Delphi. A small money contribution to get something they need is > a small price to pay. I showed my company the price saving for a 5 > person development team. They couldn’t believe the savings, and allowed > me to

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Graeme Geldenhuys
On 22/03/2019 13:29, LacaK wrote: > As far as we are company owned by state we have relative > strong restrictive policy for what we can spend money ;-| Tell them how much money (£2000+) they save per developer by using FPC versus Delphi. A small money contribution to get something they need is

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread LacaK
(I am asking because in future probably in our company we will need generate PDF invoices which should be digitaly signed) I've looked at the documentation and it is quite doable to implement this. Could be a nice task, but it will and somewhere at the bottom of my to-do list until I

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Joost van der Sluis
On 3/22/19 12:22 PM, LacaK wrote: How complicated would be add support for digital signing of PDF documents? I briefly looked at that when I implemented fpPDF, and that is quite tricky.  Plus I don't fully understand all the requirements yet. :-( ok thank you (I am asking because in future

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread LacaK
(but looking into PDF there is still in FontDescriptor wrong MissingWidth attribute, which does not goes into play AFAICS) What do you think is wrong with it? Look into test-noembed.pdf which I have attached to prior email. There is: 10 0 obj << /Type /FontDescriptor /FontName /Courier#20New

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Graeme Geldenhuys
On 22/03/2019 07:16, LacaK wrote: > (but looking into PDF there is still in FontDescriptor wrong > MissingWidth attribute, which does not goes into play AFAICS) What do you think is wrong with it? On my side it is set to 600, which as far as I can see is correct for cour.ttf subset embedded

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread Michael Van Canneyt
On Fri, 22 Mar 2019, LacaK wrote: I attached 2 patches to the bug tracker which solves the problem for me. 1. I can confirm, that in my case it is fixed for NO-embedded case only. For embedded fonts case there is still small issue (some characters are okay, some are shifted) - see

Re: [fpc-pascal] fpPDF and support of Latin2 charset

2019-03-22 Thread LacaK
I attached 2 patches to the bug tracker which solves the problem for me. 1. I can confirm, that in my case it is fixed for NO-embedded case only. For embedded fonts case there is still small issue (some characters are okay, some are shifted) - see attachments (but looking into PDF there is