It's a fallacy to believe that ChatGPT or Claude would look at some encoded, unfit for the purpose, text representation. ChatGPT (and the OpenAI Responses API, I believe) in particular renders the PDF pages in addition to text extraction, so the whole premise of "But now most PDFs end up in an LLM" is wrong from the start. If you were to be processing PDFs in a pure LLM stage, there are options like Docling or LlamaParse for proper preprocessing.
Adaptive PDFs
81–90 of 91 posts
Re: Adaptive PDFs
#82Earlier quoted context omitted.
> Just because everything is a potential threat vector now Sweet Summer child... it always was the case. There is no "now" just because there are new tools.
It was always the case that a mean person could throw a rock at you and you'd die. Therefore, nuclear weapons are nothing to be worried about.
It's 2 different statements. The first is true, even if you don't like it. The "therefore" is something you completely made up to make your point and imply something I neither said nor suggested.
You might not like it either but an arm race isn't new. The tools changed but competition, and thus threats, remain.
Re: Adaptive PDFs
#83Earlier quoted context omitted.
It was always the case that a mean person could throw a rock at you and you'd die. Therefore, nuclear weapons are nothing to be worried about.
This is a form of argument known as reductio ad absurdum. I see it more and more frequently now, often in dismissal of a fairly throughtful point of view, usually with a mocking and disdainful tone, and therefore nuclear weapons are nothing to worry about.
I'm not sure if reductio ad absurdum was about my point or theirs but just to be explicit, I didn't say it wasn't a problem or a big deal, only that that threats and competitions are not new. I clearly didn't make a moral or ethical statement about nuclear weapons.
Re: Adaptive PDFs
#84Earlier quoted context omitted.
This is a form of argument known as reductio ad absurdum. I see it more and more frequently now, often in dismissal of a fairly throughtful point of view, usually with a mocking and disdainful tone, and therefore nuclear weapons are nothing to worry about.
I'm not sure if reductio ad absurdum was about my point or theirs but just to be explicit, I didn't say it wasn't a problem or a big deal, only that that threats and competitions are not new. I clearly didn't make a moral or ethical statement about nuclear weapons.
Their's.
Re: Adaptive PDFs
#85Earlier quoted context omitted.
It was always the case that a mean person could throw a rock at you and you'd die. Therefore, nuclear weapons are nothing to be worried about.
It's 2 different statements. The first is true, even if you don't like it. The "therefore" is something you completely made up to make your point and imply something I neither said nor suggested. You might not like it either but an arm race isn't new. The tools changed but competition, and thus threats, remain.
I agree with you, but argue with the form of the person we both replied to. Alhough I would prefer universal peace and international morality, I maintain a generally neutral position on nuclear arms. I am also neutral on the evergreen innocent idiocies of youthfulness.
Re: Adaptive PDFs
#86It would be great to see some benchmark how it improve the agent. Like agent will be better at getting information from such data or what? Otherwise what is the goal of using it
Re: Adaptive PDFs
#87Very interesting, but also quite sad that today's renderers ignore the finer points of the specification. On a related note, I like the ability of good old HTML to be able to change text for different human readers, based on their chosen locale. With this I can change units such as litres to 'fluid flagon ounces' or whatever it is they use in the USA, or I can drop in a friendly greeting in a foreign language. I have…
What part of HTML is letting you adapt e.g. units of measurement by locale? Presumably there's also CSD and JS involved?
Imagine an article about sidewalks, there could be an explainer for Brits that explains that 'they mean the pavement' and another about 'customary units'. Americans would not need the explainers, so they could be made visible only to international readers with:
[lang=en-us] aside { display:none; }Re: Adaptive PDFs
#88Earlier quoted context omitted.
What part of HTML is letting you adapt e.g. units of measurement by locale? Presumably there's also CSD and JS involved?
Not sure about HTML, but you can use ` ` [1] in SVG and it will display localized text based on the `system’anguage` property. [1]: https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/E...
Switch has some gnarly options with it, and I do want to find an excuse to use it in my 'SVG embroidery sampler'.
Flags are a possibility, although I only have the UK flag in my SVG sprite sheet thus far.
I will have to see if I can build a usefully stylish locale switcher that gets it right the first time due to browser locale, yet is changeable, with option stored in local storage, all inside the SVG Shadow DOM...
Re: Adaptive PDFs
#89Earlier quoted context omitted.
What part of HTML is letting you adapt e.g. units of measurement by locale? Presumably there's also CSD and JS involved?
Imagine an article about sidewalks, there could be an explainer for Brits that explains that 'they mean the pavement' and another about 'customary units'. Americans would not need the explainers, so they could be made visible only to international readers with: [lang=en-us] aside { display:none; }
But lang in this case would be a property of the document itself, not the user agent, right?
I can't see a way in CSS to detect the user agent preferred language, but you could do this in JS and add another attribute to the document or whatever.
Re: Adaptive PDFs
#90Earlier quoted context omitted.
Imagine an article about sidewalks, there could be an explainer for Brits that explains that 'they mean the pavement' and another about 'customary units'. Americans would not need the explainers, so they could be made visible only to international readers with: [lang=en-us] aside { display:none; }
But lang in this case would be a property of the document itself, not the user agent, right? I can't see a way in CSS to detect the user agent preferred language, but you could do this in JS and add another attribute to the document or whatever.
Correct!
It has been a year since I last checked, and I did use JS and 'navigator'.
However, importantly for me, I was able to avoid a trip back to the server for the few bits I wanted - introduction - in different locales.