Microsoft Adds Adobe Acrobat PDF Tech To Its Edge Browser (betanews.com) 57
BetaNews: Yesterday, Microsoft announced it would be bringing AI to its Edge browser thanks to a partnership with ChatGPT owner OpenAI. Today the software giant adds something that many people will be less keen on -- Acrobat PDF technology. Describing the move as the next step to in their "commitment to transform the future of digital work and life," Microsoft and Adobe say this addition will give uses a unique PDF experience with extra features that will remain free of charge. By powering the built-in PDF reader with the Adobe Acrobat PDF engine, Microsoft says users will benefit from "higher fidelity for more accurate colors and graphics, improved performance, strong security for PDF handling, and greater accessibility -- including better text selection and read-aloud narration."
Re: (Score:3)
Re: (Score:2)
Adobe has money? Well, maybe, but if Microsoft wants some of that dwindling cash reserve then it shows just how much trouble Microsoft is in with its own cash.
Adobe reader is 1) buggy, 2) insecure due to faults, 3) insecure by design, 4) amazingly slow, 5) will modify your PDF documents despite it being a read-only format and no user modifications were asked for, 6) will not read many properly formatted PDF documents. On the plus side, Adobe Reader is an excellent case study of how not to create a user in
Re: Great idea! (Score:3)
Re: (Score:2)
Re: Great idea! (Score:2)
Re: (Score:2, Interesting)
You realize they still don't ship a compliant Pdf reader with Chrome or Firefox. They are missing a ton of security features and support for advance forms.
Chrome has enough compliance to view/print PDFs, including "advanced" features such as copy/paste and rotate which require a paid subscription to perform in Acrobat reader.
The fact Edge lets you rotate a PDF without a monthly fee was one of the exceedingly rare reasons we have (had?) left to open the stupid thing.
The only problem I've ever had with Chrome and PDFs is keeping windows from resetting the default .pdf handler back to Edge every two weeks. Which isn't even a Chrome problem, it's a windows probl
Re: (Score:2)
You realize they still don't ship a compliant Pdf reader with Chrome or Firefox. They are missing a ton of security features and support for advance forms.
I don't want support for advanced PDF forms in my web browser.
Web browsers have HTML and HTML forms. If any form filling needs to be done online they can use HTML.
Re: (Score:1)
> it's one of the most notoriously buggy insecure pieces of software ever made
If it's for read-only content, it shouldn't have notable security holes (as long as scrubbed of org meta-data). It's the interactive forms etc. that create the leaks. If they had bundled a read-only "reader", that should be fine.
Re: (Score:2)
Just when you think Edge might become a good web browser they have to do this and send it all the way down the big snake back to square 1.
Exploit vector (Score:1)
I seem to remember getting pwned once back in the day by a drive-by PDF exploit. That was a pain to remove.
Use a text format for online text - NOT PDF! (Score:2)
Anything that encourages people to use it for online text instead of HTML or ( imagine! ) plain text is a BAD THING.
Expect more 100MB PDF emails from the boss' secretary containing a single sentence...
Doesn't scale (Score:1)
> PDF is a horrible format for online text [so avoid it].
You can't expect all content creators to be UIX/HTML/CSS experts, or hire one. That doesn't scale from a staffing perspective. WYSYWIG and paper-friendly content creation is far cheaper to do than "proper" HTML documents.
As a tax payer, I wouldn't want to pay significantly more taxes if say all the online IRS or DMV documentation content required hiring an army of HTML experts to HTML-atize. For very common content, it makes sense for the most com
Re:Doesn't scale [correction] (Score:1)
Minor Correction of: For very common content, it makes sense for the most common stuff, but not obscure and niche docs.
Should be: For very common content it makes sense, but not obscure and niche docs.
Re: (Score:1)
> You can't expect all content creators to be UIX/HTML/CSS experts,
You can't expect 'content creators' to be PDF experts either.
Tools like this mean they will easily, dumbly, unthinkingly PRODUCE pdfs.
Instead of using tools that allow them to easily PRODUCE HTML or plain text.
Re: (Score:2)
-At some point this thread enters troll territory.
Re: (Score:1)
Because they have the necessary expertise and experience to do it right. But multiply that education time by say 500 workers, and it ... doesn't scale.
Re: (Score:2)
> You can't expect 'content creators' to be PDF experts either.
Most use MS-Office or clones of. They don't have to be PDF experts to make a PDF from those.
> Instead of using tools that allow them to easily PRODUCE HTML or plain text.
Pilot such a tool in a typical office environment and if-and-when the tool works, I'll agree to spreading it.
One common complaint of similar such tools is that they are not WYSIWYG, especially when printing. It's one way on the author's screen and too different on paper or
Re: (Score:1)
For one, it was intended as a hypothetical example. Two I said commonly used content warrants HTMLization. Those links may be commonly used, but I have no click count report on them. And perhaps IRS has a good or domain-fit content management system that most trained on such that they don't need to use MS-Office as often.
Re: (Score:2)
Try formatting logic or math in HTML, I'd rather eat a broom.
Re: (Score:2)
Re: (Score:2)
PDF isn't used for online text, it's used to render printable content.
Expect more 100MB PDF emails from the boss' secretary containing a single sentence...
The problem isn't PDF, or any software capabilities. The problem is your boss's secretary. ... Or maybe the problem is you upset her and she's doing it on purpose.
Re: (Score:1)
FTFY
The problem is giving people the ability to produce PDFs more easily means more useless PDFs will be produced, and put in web pages and emailed.
Re: (Score:2)
Re: (Score:2)
PDF needs to go the way of Flash
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
Re: (Score:1)
Bringing back Adobe tech (Score:3)
Re: (Score:2)
Flash and Java Applets scratched certain itches that HTML/DOM/CSS/JS have a hard time solving well. The one-size-fits-all thinking of "everything through HTML" has been a big mistake. For example, web lacks consistent position control of text and missing roughly 15 common GUI widgets/idioms. We need extra or supplemental standards; web is failing or giving us a "clunky tax".
Re: (Score:2)
Flash might have survived if it became more of an open standard with detailed specifications that anyone could implement without reverse engineering something. Probably not for advertising, video, or general purpose websites, but for some things where it has a technical advantage.
Re: (Score:2)
For example, web lacks consistent position control of text
That's because web windows can be resized arbitrarily.
(which is a good thing)
Right tool/feature for the job (Score:2)
I'm okay with optional auto-flow, I just don't want it forced (the only option). DOM absolute coordinates are defective, especially for text. Absolute text positioning is also needed for charts, such as flow-charts, ERD charts, etc.
Why is ANY viewer/format included? (Score:2)
In my opinion, no web browser should be in bed with any format and should not directly include ANY player/viewer/editor natively in the browser. Plugins to the applications of your choice is the only correct way.
Re: (Score:2)
Re: (Score:2)
In my opinion, no web browser should be in bed with any format
Indeed, a browser should just render a blank screen with text. No images, no videos, no audio, nothing. Those are all formats and we don't want browsers to be in bed when it should be on screen. It's not the browser's job to sleep on the job. It should just download everything and require you to open the files in a native application.
Now excuse me while I fire up the photo viewer to see which of the buttons on the screen say submit*.
*Note I'm being facetious, I know the buttons aren't graphics... on this si
Edge already had some advanced features (Score:2)
Edge already had advanced features like the ability to annotate PDFS. I've used it quite a few times to fill out PDFs that were sent to me by people. Works so much better than printing them out and writing by hand.
I also have a drawing table which is great for quickly adding notes to PDFs.
Re: (Score:2)
I'm worried about this honestly. Edge's PDF reader / editor is far better than Adobe's slow piece of crap. Sure the latter supports all sorts of weird and wonderful encryption schemes, and Edge has basically no colour management on PDFs to speak of, but honestly if I ever get stuck I can always open Acrobat for one of those files.
Re: (Score:2)
Edge already had advanced features like the ability to annotate PDFS. I've used it quite a few times to fill out PDFs that were sent to me by people. Works so much better than printing them out and writing by hand.
I also have a drawing table which is great for quickly adding notes to PDFs.
ie. Adding "More Adobe!" is a step backwards.
Does any of you realize Adobe doesn't manage this? (Score:1)
Adobe doesn't manage the Adobe PDF library code - That is managed by Datalogics out of Chicago. Adobe's efforts stops at the edge of either Windows or Mac OS (I can't remember which). Datalogics handles porting and integrating the library to other platforms.
As for the the moron (@greytree) that thinks that HTML is superior to PDF - doesn't understand the use case for neither HTML nor PDF. Using PDF for HTML-type work via PDF Forms, doesn't work very well (stupid and sucks). Using HTML for PDF-type wo
Re: (Score:2)
> PDF predates HTML.
Indeed. When Tim Berners-Lee was inventing HTML, what was drawing the dots on his NeXT system's screen? Display Postscript.
leaks (Score:2)
So every time I run Edge it leaks info to Adobe? Good to know, I'll avoid Edge even more now.
Re: (Score:2)
Enterprises will love it. (Score:3)
As much as I Loathe Acrobat, this move by Microsoft is going to push a lot of enterprises towards Edge, especially if it means they can finally ditch installing Acrobat Reader.
I know in our organization, 3rd party PDF readers including Edge, do not support the full feature set of Acrobat. Specifically electronically signed signatures via certificate. We pretty much had to either set edge to download every PDF our users run into and open them in Acrobat Reader, or force certain sites to IE compatibility mode. Edge supporting that alone would allow us to finally ditch IE for some of our intranet purchasing forms.
Re: (Score:2)
As much as I Loathe Acrobat, this move by Microsoft is going to push a lot of enterprises towards Edge, especially if it means they can finally ditch installing Acrobat Reader.
How is this "not installing Acrobat Reader"?
Re: (Score:2)
Re: (Score:2)
This would be true for us.... except I suspect this PDF feature in Edge won't support third-party addons for Acrobat Reader, like the DRM plugin we have to install to allow our users to read PDFs from certain engineering/scientific sources.
Instead we're forced to use policies that force Edge to download PDFs instead of display them, and ensure that Acrobat remains associated with PDFs, otherwise we get tickets about how these PDFs won't display.
Absolutely, if we could avoid installing Reader I'd do it in a
Interesting (Score:2)
Who patches? (Score:2)
So who is responsible if there is a security issue in the adobe engine?
Will MS be able and willing to create a patch and send the update? Or will we have to wait for Adobe to create a patch, MS to verify / test (assuming they even do that nowadays) before releasing it to users?