El 5/3/24 a las 4:23, Luc escribió:
> On Tue, 5 Mar 2024 00:15:56 -0000 (UTC), Rich wrote:
>
>> Unless the merged image fits on a single sheet of paper (or you are ok
>> with shrinking it to fit) an image that is too large has to be split
>> up, by you the programmer, before being placed onto the output "pages".
>> Pdf4tcl will shrink it to fit for you, but it will not break a single
>> image up into page size chunks.
>
>
> Another point in favor of the RTF format. A word processor can handle
> automatic page breaks very well.
>
> I will add RTF.
>

Another possibility is to generate HTML and use wkhtmltopdf (available
on Windows and Linux) to generate PDF. No need for coordinates, pixels,
line and page breaks, and the likes.

HTH.

On Tue, 5 Mar 2024 09:06:34 +0100, Manuel Collado wrote:

>Another possibility is to generate HTML and use wkhtmltopdf (available
>on Windows and Linux) to generate PDF. No need for coordinates, pixels,
>line and page breaks, and the likes.
>
>HTH.

Interesting addition to my personal toolbox, but I probably can't
include and distribute it because it's licensed under the LGPLv3 and
my application is licensed under BSD terms.

Thank you.

--
Luc
>>

Luc <luc@sep.invalid> wrote:
> On Tue, 5 Mar 2024 09:06:34 +0100, Manuel Collado wrote:
>
>>Another possibility is to generate HTML and use wkhtmltopdf (available
>>on Windows and Linux) to generate PDF. No need for coordinates, pixels,
>>line and page breaks, and the likes.
>>
>>HTH.
>
> Interesting addition to my personal toolbox, but I probably can't
> include and distribute it because it's licensed under the LGPLv3 and
> my application is licensed under BSD terms.

If you make no changes to it (wkhtmltopdf) and supply the licence file
for it as well, there should be no issues with you distributing it.

Given that all you'd be doing is using it the same as any other end
user (launching it with an html input file) there is likely no issue.

Bundling it, in its own sub-directory, unmodified, with your bundle
should not cause your code to need to be relicenced. And if your
entire interface is "exec wkhtmltopdf /tmp/htmlfile" you are not adding
any of it into any of your source files.

If you want to be more 'careful' then supply it as a second,
dependency, tar/zip file that has to also be installed for your code to
work. Then it is not part of your "bundle" at all.

On Tue, 5 Mar 2024 16:49:08 -0000 (UTC), Rich wrote:

>If you make no changes to it (wkhtmltopdf) and supply the licence file
>for it as well, there should be no issues with you distributing it.
>
>Given that all you'd be doing is using it the same as any other end
>user (launching it with an html input file) there is likely no issue.
>
>Bundling it, in its own sub-directory, unmodified, with your bundle
>should not cause your code to need to be relicenced. And if your
>entire interface is "exec wkhtmltopdf /tmp/htmlfile" you are not adding
>any of it into any of your source files.
>
>If you want to be more 'careful' then supply it as a second,
>dependency, tar/zip file that has to also be installed for your code to
>work. Then it is not part of your "bundle" at all.

I intend to release both the source code as any Tcler would have it and
Freewrap packages which is better for common users and I can bundle a
lot of stuff in it if necessary.

The Freewrap version is mostly worry-free since I can just bundle
anything I want and neither me nor the user has to fret. I just don't
know how distro packagers will likely behave when they're met with
the two options so I have acquired this tendency to avoid extensions,
to minimize the number of dependencies. I hate dependencies and how
Linux is so enamored with them. I am a little obsessed with ideas of
compatibility and I will not change. I am that grumpy old man in plaid
who says,

"You know what the problem with the world is, Ennid? It's that nobody
cares. That is what is wrong with the world."

--
Luc
>>