- #When possible use the default text encoding in replies pdf#
- #When possible use the default text encoding in replies pro#
- #When possible use the default text encoding in replies iso#
Thank you both for your insights and expertise.
#When possible use the default text encoding in replies pro#
Also Arial can be banished for opentype versions of Myriad Pro or Heveltica Neue with more typographic flexibility. And at the end of the day, the client will have a fresh new original docment that can be freely revised, which is the right way to do it.
#When possible use the default text encoding in replies iso#
So I think the path of least resistance is to re-create these documents with the fiull suite of InDesign's layout tools, and re-set the text I can extract, recover, or OCR. I have received an email in HTML format, with what looks to be greek ISO encoding (iso-8859-7)When I click reply, the composed email is automatically set to same (Greek ISO) encoding, even though normally all my compose emails are in unicode.
![when possible use the default text encoding in replies when possible use the default text encoding in replies](https://alltechnoblog.com/wp-content/uploads/2014/11/Image-7.png)
So we won't have to have a copy editor retype all the text from the entire document. And bless the Gods of Design, the " Copy witth Formatting" feature in Acrobat DC turns out to recover about 90% of the text from individual pages. I can get reasonable OCR from 600-dpi exports (vs the first attempt at 300 dpi) of individual pages, which I can also use to recover a multitude of individual inline graphics. This approach has it's limitatoons, and lacks design flexibility. The various options are all varying degrees of tedious, bringing in individual pages of the orignal and pasting over the edits on a new layer. I discovered the problem using the otherwise excellent Markzware PDFMarkz utility to convert/import the 164-page document. I would be bat guano insane to attempt this editing within Acrobat DC. The workflow is intended to end up in InDesign. I had My suspicions, as soon as I saw "Pagemaker" in the metadata. I do relaize that having an editor manually retype the enitre document may be the eventual - but time consuming and therefore costly - solution. But I need to be able to either edit or extract this copy for the client's revisions. What's really crazy is that these LOOK like fairly common ordinary fonts. The best guess I have is this is some sort of font encoding DRM/Copy Protection scheme, or posibly some sort of variable typeface with non-standard encoding based on the "font names". The orginating application seems to be Adobe Pagemaker 6.52 / Distiller for WIndows 4.0
#When possible use the default text encoding in replies pdf#
The fairly extreme soultuon of exporting a page as a image file, creating a new PDF of the page and running OCR produces copy that would require extemsive manual correction. Even copy pasting the text or saving as a WORD or TXT file produces gibberish - even pasting into a text editor.
![when possible use the default text encoding in replies when possible use the default text encoding in replies](https://i.stack.imgur.com/fV8nt.jpg)
Attemps to replace with a common font such as Myriad, Arial, or Helvetica produces gibberish text, as is the "default" font. All the usual trick to import ot extract text, even using the otherwise excellent Marzware PDFMarz utility produces "Missing Fonts" for these. I have discovered that there is a great amount of type in these documents that is custom encoded, and have names unusual such as MSTT31c750 (Embedded Subset) Type 1 Encoding: Custom. I have received a number of multipage (150 pg+) PDF docments from a client that will require extensive revision.