printing to pdf is not a feature of itunes.
it's a feature of macos itself and applies to *any* app that can print.
The key question is whether that PDF is essentially text or images.
no it isn't.
how in the world could a *list* of apps be images?? images of what?
pngs of the icons but no text anywhere?
printing to pdf is not a feature of itunes.
it's a feature of macos itself and applies to *any* app that can print.
Thank you for clarifying that the print-to-PDF is not coming directly out
of iTunes, but from the OS.
Many apps have a print-to-PDF feature (e.g., MS Office), while the three desktop-based operating systems (linux, windows, and Mac) have native PDF-printing engines.
The key question is whether that PDF is essentially text or images.
no it isn't.
how in the world could a *list* of apps be images?? images of what?
pngs of the icons but no text anywhere?
I thank you for suggesting we use iTunes to output the list of apps
installed on iOS devices to a PDF file, and then to save that PDF file as text.
I have a *lot* of experience decomposing PDF files into their text components.
It's a topic which has been discussed very many times on the comp.text.pdf Usenet newsgroup.
Sometimes it's easy.
Sometimes it's not easy.
When it's easy, the output you want is saved in the text results.
When it's not easy, the output is saved as images.
c. Does the iTunes output to PDF contain "text" or "images"?
Text
the real question is what would the images even *be*?
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF engine. But I could be wrong.
On Thu, 21 Jul 2016 18:30:40 -0400, nospam wrote:
c. Does the iTunes output to PDF contain "text" or "images"?
Text
the real question is what would the images even *be*?
The folks at comp.text.pdf can probably explain this better than I, but suffice to say when a PDF is created, it can be rasterized bitmaps of
'text' images, or it can contain the actual text.
The comp.text.pdf folks will be able to explain this better than I.
c. Does the iTunes output to PDF contain "text" or "images"?
Text
the real question is what would the images even *be*?
The folks at comp.text.pdf can probably explain this better than I, but suffice to say when a PDF is created, it can be rasterized bitmaps of
'text' images, or it can contain the actual text.
only one has a native pdf engine, and that's macos.
On Fri, 22 Jul 2016 00:49:37 -0400, nospam wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF engine. But I could be wrong.
You're a fucking joke.
LOL... Dream on. You're in over your head.
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF engine. But I could be wrong.
LOL... Dream on. You're in over your head.
In article <dvdrn0Fi79jU1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF
engine. But I could be wrong.
LOL... Dream on. You're in over your head.
that's no way to talk about a harvard grad :)
On Fri, 22 Jul 2016 00:49:37 -0400, nospam wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF engine. But I could be wrong.
In article <dvdrn0Fi79jU1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native CUPS-based PDF
engine. But I could be wrong.
LOL... Dream on. You're in over your head.
that's no way to talk about a harvard grad :)
In article <nmsc1i$ra3$4@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native
CUPS-based PDF engine. But I could be wrong.
you are wrong. again.
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native
CUPS-based PDF engine. But I could be wrong.
you are wrong. again.
Actually Aardvarks is right: there is a CUPS print-to-PDF driver. Not specifically native to Linux, though; native to CUPS, which is cross-platform.
On 07/22/2016 06:52 AM, nospam wrote:
In article <nmsc1i$ra3$4@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native
CUPS-based PDF engine. But I could be wrong.
you are wrong. again.
Actually Aardvarks is right: there is a CUPS print-to-PDF driver. Not specifically native to Linux, though; native to CUPS, which is cross-platform.
In article <e11jnpF6iqtU1@mid.individual.net>, Peter Flynn <peter@silmaril.ie> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native
CUPS-based PDF engine. But I could be wrong.
you are wrong. again.
Actually Aardvarks is right: there is a CUPS print-to-PDF driver. Not
specifically native to Linux, though; native to CUPS, which is
cross-platform.
if it's not native to linux then it has to be installed, which means
he's wrong, as are you.
on macos, there's nothing to install. pdf is a native format.
on linux, pdf is *not* a native format.
On 10/08/16 22:18, nospam wrote:
In article <e11jnpF6iqtU1@mid.individual.net>, Peter Flynn
<peter@silmaril.ie> wrote:
only one has a native pdf engine, and that's macos.
It has been a while, but I think Linux also has a native
CUPS-based PDF engine. But I could be wrong.
you are wrong. again.
Actually Aardvarks is right: there is a CUPS print-to-PDF driver. Not
specifically native to Linux, though; native to CUPS, which is
cross-platform.
if it's not native to linux then it has to be installed, which means
he's wrong, as are you.
If by "native" you mean "installed by default during a fresh install of
the OS" then that would be correct.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 33:15:48 |
Calls: | 6,648 |
Calls today: | 3 |
Files: | 12,193 |
Messages: | 5,328,709 |