On 28/03/2019 17:39, Bo Berglund wrote:
> The link you provided in your signature gets me to a place where
> versions are displayed and the last one is 1.4.1 from 2015-09-02.
> Is this a final version not in need of any new stuff?
Is software ever "finished" Nope! :)
I've been a bit lazy maki
On Fri, 22 Mar 2019 20:48:25 +, Graeme Geldenhuys
wrote:
>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
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 ln
> 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 d
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
a
(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 need
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 pro
(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
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 font.
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 attachm
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
I attached 2 patches to the bug tracker which solves the problem for me.
Regards,
Graeme
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/
My public PGP key: http://tinyurl.com/graeme-pgp
___
fpc-pasca
On 21/03/2019 13:20, LacaK wrote:
> I think that problem is related to font parsing. As I wrote in comment
> to bug report #35251 there is incorrectly extracted information about
> char Widths ... look into attached generated PDF there ...
Ah yes, I see what you mean. Apologies, I didn’t read th
I am trying work with fpPDF. I can create PDF document, but character
out of ASCII range are displayed wrong (in PDF file they are stored as
UTF8).
First things first... what version of FPC are you using? FPC 3.0.4 or
FPC 3.1.1 - just so I know what code to look at.
I tried both versions 3.0.
On 19/03/2019 08:46, LacaK wrote:
> I am trying work with fpPDF. I can create PDF document, but character
> out of ASCII range are displayed wrong (in PDF file they are stored as
> UTF8).
First things first... what version of FPC are you using? FPC 3.0.4 or
FPC 3.1.1 - just so I know what code t
El 19/03/2019 a las 15:00, LacaK escribió:
It seems that there is problem specific to CourierNew font (cour.ttf).
With Arial (arial.ttf) it works as expected.
Attached program which demonstrates problem.
Hello,
Can you send me by direct mail the pdf result for that program ? I´ll
try to sp
I suspect that the Arial font has unicode glyphs, and courier not.
I do not know, but with other fonts: Arial, Verdana, Consolas it works
as expected. Do you think, that Courier New is only exception?
When I look at
https://docs.microsoft.com/en-us/typography/font-list/courier-new I do
n
Is there way how to get correct PDF file WITHOUT embedding full
Courier font?
You can embed only the needed characters for every font ?
Probably yes, but fpPDF will not handle this automatically? AFAIK I
can not control this.
But why I get unreadable characters? What I am doing wrong ?
On Wed, 20 Mar 2019, LacaK wrote:
Is there way how to get correct PDF file WITHOUT embedding full
Courier font?
You can embed only the needed characters for every font ?
Probably yes, but fpPDF will not handle this automatically? AFAIK I
can not control this.
But why I get unreadable
Is there way how to get correct PDF file WITHOUT embedding full
Courier font?
You can embed only the needed characters for every font ?
Probably yes, but fpPDF will not handle this automatically? AFAIK I
can not control this.
But why I get unreadable characters? What I am doing wrong ?
Is there way how to get correct PDF file WITHOUT embedding full
Courier font?
You can embed only the needed characters for every font ?
Probably yes, but fpPDF will not handle this automatically? AFAIK I
can not control this.
But why I get unreadable characters? What I am doing wrong ?
I
Hi,
I am trying work with fpPDF. I can create PDF document, but character
out of ASCII range are displayed wrong (in PDF file they are stored
as UTF8).
Probably it is because I use standard Courier font, which is
expecting only "Latin characters" ? I use:
FontIndex := PDF.AddFont('Courie
On Tue, 19 Mar 2019, LacaK wrote:
Hi,
I am trying work with fpPDF. I can create PDF document, but character out of
ASCII range are displayed wrong (in PDF file they are stored as UTF8).
Probably it is because I use standard Courier font, which is expecting only
"Latin characters" ? I use:
23 matches
Mail list logo
