xPDFSearch 1.45 - Content plugin to search text in PDF files

[petermad]

2Ovg

How were you able to do that? I haven't this plugin in the list under File -> Change Attributes -> Change plugin attributes.

Maybe like this: https://madsenworld.dk/tcmd/xpdfsearchattib.png

[Ovg]

2petermad
Bingo! Many thanks! You save my life!

PS: Many, many THANKS for the Extended Menus!

[zeeko]

Version 1.37

ADDED

• Load options from xPDFSearch.ini file in directory where plugin is located.
  If xPDFSearch.ini is not found, load options from TC content plugin ini file.

• [xPDFSearch] AppendExtensionLevel - find PDF Extension Level and append it to PDF Version:
  PDF 1.7 Extension Level 3 = 1.73

• new field: Conformance - PDF/A, PDF/E, PDF/X

CHANGED

• improved PDF Date parsing, allow dates that don't start with D:

https://github.com/tgotic/xPDFSearch/releases/download/v1.37/wdx_xpdfsearch_1.37.zip

2Usher
CreationDate (D:191070218162540) is supported. It is not Unix timestamp in milliseconds. Format is CCYYYMMDDhhmmss.
19107 is 19 * 100 + 107 = 2007
CreationDate(11/17/2006 14:50:52) is not supported. There are just too many variations of date formats.

[Usher]

Version 1.37
CHANGED

• improved PDF Date parsing, allow dates that don't start with D:

Thanks.

2Usher
CreationDate (D:191070218162540) is supported. It is not Unix timestamp in milliseconds. Format is CCYYYMMDDhhmmss.
19107 is 19 * 100 + 107 = 2007

Sorry for misleading info. I just overlooked other metadata in a file:
* Producer (Acrobat Distiller 3.0 for Windows)
* Creator (Adobe PageMaker 6.52)
Distiller was released in 1996, PageMaker in 1997, so both could have Y2k bugs.
However, the number is a valid Unix timestamp in microseconds:

Assuming that this timestamp is in microseconds (1/1,000,000 second):
GMT: Wednesday, 21 January 1976 11:03:38.162

For me it's a possible result as I have files with the following timestamps:
* CreationDate (D:198112131236115+02'00')
* ModDate (D:19811213123825+02'00')
* Producer (OpenOffice 1.1.1.4)
or similar. If 1981 is OK (it should be at least 2004) what could be wrong with 1976?

CreationDate(11/17/2006 14:50:52) is not supported. There are just too many variations of date formats.

I know that it's ambiguous. However, can you display it as a text string in a custom column? SumatraPDF shows the value as is (without conversion) in such cases.

[petermad]

2zeeko

xPDFSearch.lng file with updated Danish translation for v. 1.37 can be downloaded at https://madsenworld.dk/tcmd/xPDFSearch.zip

[zeeko]

2petermad
Could you please add/translate new fields for the new version:
CreatedRaw=
ModifiedRaw=
These are Created/Modified date strings as written in PDF document as Usher suggested.
There will be ini option to remove D: from date string.

[petermad]

2zeeko
Updated translation can be downloaded at https://madsenworld.dk/tcmd/xPDFSearchB.zip

[zeeko]

Version 1.38

ADDED

• New fields: CreatedRaw and ModifiedRaw (date strings from PDF)

• [xPDFSearch] RemoveDateRawDColon - remove D: from date string

CHANGED

• Relaxed date year in Created and Modified fields

• Updated Danish and Croatian translation

https://github.com/tgotic/xPDFSearch/releases/download/v1.38/wdx_xpdfsearch_1.38.zip

[Usher]

2zeeko
Great! Now it works almost perfectly. I have 14k+ PDFs to test, so I will send more details in the next year

[Lefteous]

2zeeko
After all these years I'm still getting mails why there are two versions of the same plugin and why things are like that and not like that. Any ideas how we can solve this?

[zeeko]

2Lefteous
By two versions, you probably mean v1.11 and v1.3x versions and not XP/W7+ versions of v1.36/1.36a.
How would you like to solve this situation?
Possibilities:

• I would do pull request so you could sync xPDFSearch GitHub repositories and you would continue to release new versions. There were no progress on https://github.com/lefteous-tc/xPDFSearch since my last pull request three years ago, and some users on this forum asked me to fork.

• I would continue to release new versions and inform you or moderators to change title of this topic to the latest published version and update link to the plugin in the first post. There would be only one version (x86+x64) and you could post some of these "like that and not like that" mails on this forum so maybe something could be done about them.

• You have your ideas about plugin and would like me to change plugin name and start new forum topic.

[Lefteous]

2zeeko
I would propose to split this thread (by moderators) at the point where you forked the plugin. You don't have to use a new name, but it might be less confusing, so this would be my preferred solution (maybe just xpdf?).
I would really like to contribute something but unfortunately I don't have the time anymore.

[white]

Moderator message from: white » 2023-01-10, 23:31 UTC

I would propose to split this thread (by moderators) at the point where you forked the plugin.

Done.

Lefteous' thread is still:
xPDFSearch 1.11 - Content plugin to search text in PDF files

New thread is:
xPDFSearch 1.38 - Content plugin to search text in PDF files

2zeeko
You can edit first post and update it with each new version.

[consistency]

@zeeko

bugreport: trying to rename multiple files with the multirename tool while using this plugin leads to "Error, could not rename the files shown in bold!". it looks like the plugin locks the file by accessing it so tc can't rename it.
[edit]
my workaround: using "edit filenames" in the multi rename tool (small folder icon below the questionmark icon) to export the filenames to a file and then rename by "load names from file"
[/edit]

feature request: would be nice to have issues enabled on github, the user experience would be enhanced by beeing able to subscribe specific bugs/feature requests and getting notification emails. this makes following much easier.

[Ovg]

2consistency

To use xPDFSearch in Multi-Rename Tool, you need to add/change content plugin ini file (usually %COMMANDER_PATH%\contplug.ini):

Code: Select all

[xPDFSearch]
NoCache=1

and restart TC.
This option enables renaming and changing attributes, but slows down fields extraction.