New content plugin cputil (chars from different codepage)

[ts4242]

2ghisler(Author)

Can you please make (if you have free time) cputil for 64-bit version.

Moderator message

This and the following 5 posts were moved from 64-bit plugins (download list).

Hacker (Moderator)

[tbeu]

Can you please make (if you have free time) cputil for 64-bit version.

Test this. It is only a recompile without validation so far.

[ts4242]

2tbeu

Sorry, it doesn't work, TC accept the dll but I cannot use it in MRT or to create custom column (it is not added tp plugin menu list)

[tbeu]

2tbeu

Sorry, it doesn't work, TC accept the dll but I cannot use it in MRT or to create custom column (it is not added tp plugin menu list)

Arg, stupid plugin installation. Check your wincmd.ini and add n=1 to [ContenPlugins64] where n is the number of cputil.wdx in [ContenPlugins]. See my example

Code: Select all

[ContentPlugins]
...
38=c:\MyProgramFiles\wincmd\Plugins\cputil\cputil.wdx
[ContentPlugins64]
...
38=1

[tbeu]

File pluginst.inf recommends defaultdir=filesys which seems kind of wrong for content plugin cputil.wdx.

[tbeu]

2ghisler
Can you please make official update of cputil plugin?

[leopoldus]

Hello,
As much as I could understand from this topic, cputil can be used for either multirename tool or in regular search dialog (Alt+F7 -> Plugins). But I could not understand, which way one should use the plugin for search. There is fife different search options (modes) there in the drop-down list and many different operators for each of them. The first option "HasUnicode" = Yes/No is quite obvious, but what about the others?

Thanks!


Image: http://img11.imageshack.us/img11/102/totalcommandercputilplu.th.gif

[white]

[plugininstall]
description=copdepage utility program v1.2: Detect/replace characters from different code page
type=wdx
file=cputil.wdx
defaultdir=filesys

Typo in description: "copdepage"

As mentioned by user tbeu earlier, filesys is the wrong defaultdir.

[Compugenio]

Decades long TC user/customizer here.
I have taken Chris's x32 bit cputil code (which will not install on the x64 version of TC), cleaned it up and converted it to x64.

I provide a link to the resulting x64 source code and a link to the compiled normal .wdx64 zip (which you simply double click to install).
It works without issues, no crashes, no memory leaks, no phone home.
Run it through Virustotal if you wish.
I renamed the compiled version to codepage because it identifies it's function much better.

cputil_x64.zip
https://www.dropbox.com/scl/fi/6jk6p1u8v5mmmxb7wwruy/cputil_x64.zip?rlkey=ohh2fqhx91cz16a8pcs98rgnr&dl=0
codepage.wdx64
https://www.dropbox.com/scl/fi/h1xi56wmjc4few8p36g9d/wdx_codepage.zip?rlkey=dlbraaulp4pl14ql9uj672yw6&dl=0

If posting Dropbox links is not the way to provide these files, please advise.

[white]

I renamed the compiled version to codepage because it identifies it's function much better.

The compiled version in the source package (no exported ContentPluginUnloading function) is different from the install package (with exported ContentPluginUnloading function).
Is something not up-to-date?

[Compugenio]

Good catch, my mistake that a (working copy) compiled binary has no business being in a source package.
A definite mouse slip when trying to (re)move files around. please remove the file cputil.wdx64 from the source code.
Source packages should contain what you need to build the output, not the output itself.

The codepage.wdx64 found in wdx_codepage.zip is the correct and finalized product.
From my limited testing it works well.
Hope it serves you well and Thanks again White.

Edit: I have removed the .wdx64 file from the source code zip.

[Compugenio]

.... But I could not understand, which way one should use the plugin for search. There is fife different search options (modes) there in the drop-down list and many different operators for each of them. The first option "HasUnicode" = Yes/No is quite obvious, but what about the others?

Here are the five codepage fields with concrete examples:

**HasUnicode** — Boolean, true/false
A file named `résumé.pdf` → `True`
A file named `resume.pdf` → `False`
Useful in Search to find any file with non-ANSI characters in its name.

**NameNoUnicode** — Replaces non-ANSI characters with `_`
`Ñoño.mp3` → `__o_o.mp3`
Good for finding files that would break on systems without Unicode support.

**NameReplaceNoEnglish** — Strips accents from all scripts, converts to closest ASCII
`Ñoño.mp3` → `Nono.mp3`
`Müller.doc` → `Muller.doc`
Most aggressive — everything becomes plain ASCII regardless of your system codepage.

**NameReplaceUserUnicode** — Converts characters outside your system codepage using the `.tbl` file
On a Western (1252) system: `Привет.txt` (Cyrillic) → transliterated using `codepage1.tbl`
Characters already valid in your codepage are left alone.

**NameReplaceUserAll** — Same as above but converts everything, including characters native to your codepage
On a Western system: `Müller.doc` → also gets converted, not just Cyrillic/CJK/etc.

The most practical use for me is **HasUnicode** in Search to locate suspicious filenames, and **NameReplaceUserUnicode** in the Multi-Rename tool to batch-rename them to safe ASCII equivalents or just find them and DELETE.