XYplorer Beta Club

zer0 wrote:My initial, and current, though is that the kind of writing that XYplorer does and the kind of "Save As" Wordpad does are entirely different even though both are asked to write a TXT file.

zer0 wrote:When opened in Notepad the formatting that I would achieve if I was to open the original NFO in Wordpad and save as TXT file does not show in the converted file.

ale wrote:As a total beginner to scripting I was writing this too to learn, and had this line of code

Code: Select all

$filedata = readfile("<curbase>.nfo"); writefile("<curbase>.txt", $filedata);

or

Code: Select all

$filedata = readfile("<curbase>.nfo"); writefile("<curbase>.txt", $filedata, , tu);

to convert to Unicode

zer0 wrote:Thanks to both of you. While your code does write a text file, it does not do the same kind of conversion. When opened in Notepad the formatting that I would achieve if I was to open the original NFO in Wordpad and save as TXT file does not show in the converted file. I've attached the file in question and hope there is some remedy in this situation. My initial, and current, though is that the kind of writing that XYplorer does and the kind of "Save As" Wordpad does are entirely different even though both are asked to write a TXT file.

regexreplace $data, readfile("<curitem>"), "\n", "<crlf>"; writefile("<curpath>\<curbase>.txt", "$data");

Muroph wrote:well, they are kind of different.
AFAIK, wordpad will write the txt file using the UTF-8 encoding, while the script wil use the UTF-16 encoding.

Muroph wrote:if you try to open the nfo file on notepad you'll see the text without formatting as well.
my conclusion is that wordpad somehow fixes this.
but if you only want to read the file you can use one of xyplorer's previews.

Muroph wrote:1. you can't use <curbase>. you have to specify the whole path, and <curbase> only gives the file name without path or extension, so "<curitem>" (without .nfo) is the best choice for readfile.
it works on writefile as well, but the name of the converted file will be "file.nfo.txt". that's why i used "<curpath>\<curbase>".
2.the 1st script won't necessarily write a unicode file.
it will use ASCII encoding if possible.
the "tu" argument is what forces the script to use unicode.
3.since readfile is a function, you can put it directly inside the writefile command without having to use a variable.

ale wrote:Thanks a lot for your tips,
About the first point, I see as <curitem> is more appropriate, because it will also work for any extension but may I ask why <curbase> can't be used? or maybe it's a question about relative paths more than about <curbase>. I will say what I thought so far... readfile and writefile with a simple file name will read and write that file from and to the current folder because they accept a file name relative to the current path and I thought that if a file is selected the current path is actually the folder where the file is as we can see with something like echo ("<curpath>");

ale wrote:I think the problem with the file you posted may be related to line endings and it's not about Unicode, I tried to write a new script, may you test it? I hope it works better now

Code: Select all

regexreplace $data, readfile("<curitem>"), "\n", "<crlf>"; writefile("<curpath>\<curbase>.txt", "$data");