Code: Select all
[dut] Title=Titel Subject=Onderwerp Keywords=Sleutelwoorden Author=Auteur Application=Toepassing PDF Producer=PDF gemaakt met Number of Pages=Aantal pagina's PDF Version=PDF-versie Page Width=Pagina Breedte Page Height=Pagina Hoogte Document Start=Document Start First Row=Eerste Rij Copying Allowed=Kopieëren Toegestaan Printing Allowed=Afdrukken Toegestaan Adding Comments Allowed=Commentaar Toevoegen Toegestaan Changing Allowed=Wijzigen Toegestaan Encrypted=Versleuteld Tagged=Bevat Labels Created=Gemaakt dd Modified=Gewijzigd dd Text=Tekst mm|cm|in|pt=mm|cm|in|pt
When using the plugin supplied Title as a custom column the (TM) character is incorrectly displayed as an extra lower case o
Software Company Studio™ Product Documentation Document
Is displayed as
Software Company Studioo Product Documentation Document
Create a pdf with the title Software Company Studio™ Product Documentation Document
Go to Configuration Options in options menu
Choose Custom columns and add a new entry
add a column
Field contents [=xpdfsearch.Title]
The corrupted title will be displayed
Total Commander 7.04a
Windows XP SP2
sorry for the delayed reply. I've been busy during the week.
Unfortunately there is currently no way to display this character correctly. The problem is that the character is not part of the ANSI character set. It's part of Unicode. This standard requires Total Commander 7.5 and an updated plugin.
I hope the author don't add to much stuff into Total Commander 7.5 and releases the new major version as soon as possible.
A new version is ready for download. The new version includes important bugfixes for security problems. I have also added support for extracting Unicode metadata. Total Commander 7.50 is required to display Unicode metadata. Please note that Unicode isn't currently supported for PDfs in file paths containing Unicode and not for full text searches.
The complete list of changes can be viewed online.
Plugin page: Download, description und documentation
Thanks for this new version !
If you want to add French in your lng, here is the translation.
PDF Producer=PDF créé par
Number of Pages=Nombre de pages
Page Width=Largeur de page
Page Height=Hauteur de page
Document Start=Début du document
First Row=Première ligne
Copying Allowed=Copie autorisée
Printing Allowed=Impression autorisée
Adding Comments Allowed=Ajout de commentaires autorisé
Changing Allowed=Modification autorisée
L'important n'est pas de convaincre, mais de donner à réfléchir.
The important thing is not to convince, but to incite to think.
Hi Christian !
The problem is that the character is not part of the ANSI character set. It's part of Unicode.
• What about the ANSI #153 character ? ™ ™ ™ ™ ™ ™ ™ ™ ™
- Works here in plain text with Alt+0153…
since installing the PDF Pro (incl. Shell extensions) from www.tracker-software.com I have problems to display the correct PDF-version with xPDFSearch - it displays always "1.4". Using Shelldetails with "PDF Version" works fine.
I found two entries in the PDF-File:
Code: Select all
Code: Select all
<</PageLayout/SinglePage/Version/1.5/Outlines 570 0 R/Pages 6 0 R/PageMode/UseOutlines/Type/Catalog/ViewerPreferences<</DisplayDocTitle true>>>>
Win 10 x64
The first line of a pdf file determines the version and in a strange way, %PDF-1.4 is equivalent to Acrobat 5.0. It's the way Adobe started numbering pdf versions (1.0-1.0,1.1-2.0,1.2-3.0 ... %PDF-1.7-Adobe Acrobat 8.0) version 1.7 is the latest and last pdf spec from adobe as that version has become an open iso standard.
what was the difference xpdfs and pdf-x?
I had a bit too much time on my hands so I did a simple experiment, I created a simple text (no images) pdf file version 1.7 (acrobat 8.0), I opened it up with a Hex editor and changed the version number to 1.4 (acrobat 5.0) and I used a few tools to gather info about the file:
Acrobat reported it correctly as a 1.7 pdf
there was a line in the pdf
PDF-Xchange (both the reader and the shell extension) said it was a 1.4 pdf as did xPDFsearch. so what's the conclusion? I don't know your pdf is probably damaged as mine was and xPDF is one of the best wdx plugins around.<</Extensions<</ADBE<</BaseVersion/1.7/
I think that a found the reason of this problem: A PDF can contain two (different) infos about version(s) - at the beginning and in the "document catalog" (??).Peter wrote:... it displays always "1.4". Using Shelldetails with "PDF Version" works fine....
Take a look here:
Win 10 x64