XYplorer Beta Club

Thanks for supporting wrapped file names in the report

Tested with the latest beta, still no luck produces "?é1?ìì?? ￠ò"

So do the other two scripts.

This is really mysterious, simply forget it...

In the next beta you can try this:

Will try it upon next beta

Glad to hear that

System Locale ID: 2052 (zh-CN) Thread Locale ID: 2052 (zh-CN) Default ANSI Code Page: 936 (ANSI/OEM - 简体中文 GBK) Active ANSI Code Page: 936 (ANSI/OEM - 简体中文 GBK) Default OEM code page: 936 (ANSI/OEM - 简体中文 GBK) Active OEM Code Page: 936 (ANSI/OEM - 简体中文 GBK) Is DBCS Code Page: Yes Main Contents Font...

19.70.0.121，Still not solved! No luck with me, either. Meta tab in Info Panel: OK Raw View in Info Panel: OK (the first two lines containing the ID3 show correctly) Columns with special property (like "Tag Album", "Tag Artist", ...): no Hover box: no standard "property"...

I see it now, with Line feed on oversized filenames ticked, there are line feeds, but not within file names. Not a big problem, but a bit ambiguous, and may not be friendly for printing :) The originally expected behavior is as follows: (just for your reference, not requesting a fix for it) Wrapped ...

admin wrote: ↑10 Mar 2019 16:42 Looks garbled here (German locale):

My PC shows correctly for this file in this window (Chinese locale).
But the hover box is garbled.

It is strange that the "Meta" tab in the Info Panel is without the problem, though.

admin wrote: ↑10 Mar 2019 15:50 How does it look in Windows Explorer? Also garbled?

A confirm:

I have downloaded the file and everything looks fine in the standard "property" window of the file.

My PC is also using the CJK locale.

To be specific, "ineffective" means that:
1. With Line feed on oversized filenames ticked, no line feed occurs when there are oversized filenames.
2. Select some files, and click File | File Special | Add to Zip..., nothing happens.

As follows:

Thanks I'll spare more time reading the scripting manual.

You need to quote the full path, not only a part of it... I finally figure it out: It should be run "cmd /c command ""<curpath>"" > ""<xydata>\temp\output.txt", ,2,0; rather than run "cmd /c command ""<curpath>"" > ""<xydata...

highend wrote: ↑08 Mar 2019 12:37 And looking at how it is done for <curpath> does not help? oO

I remember it now -- Paths with whitespace should be quoted, like this "PATH".

The post has been updated.

run "cmd /c command ""<curpath>"" > <xydata>\temp\output.txt", ,2,0; You'll get into trouble if <xydata> is a path that contains a space! Thanks for the alert :) I'm a newbie in XY scripting. I think adding or removing some quotation marks will help to avoid the proble...