XYplorer Beta Club

It will not start XYplorer. For that (e.g. Win+E) you would have to change the registry, and I don't know in which way. Does anybody know? Here is an explanation about how a free open-source helper tool AutoHotkey could be used to achieve that (i.e. not by changing the registry but most probably by...

v10.90.0203 - 2012-03-23 10:55 Sorry, couldn't write back earlier. I am really very happy with a present state of encodings support. You have done very much in a very short time - thank you. I believe that this area is now quite useful for people all over the world using various encodings. Those tw...

In the days of my first programs, you had to punch cards on a real IBM card puncher, if you wanted to learn FORTRAN. Soon after I fell in love with clean structures of Pascal, which until now stayed my professional programming language number 1. So, if you have ever glanced over the uniformity and i...

Hi and welcome hicuci! Maybe you would wish to try how it looks like to use tabs inside one pane and copy/move the files between tabs, instead of using two panes. Additionally, I am using the not so well known tweak: ; Tweak: set to 1 to optimize the tree on each location change AutoOptimizeTreeRadi...

Zardoz, unfortunately neither I am an owner of iPhone, but was curious. If your iPhone does not have an option which Twisten suggests, look at this Windows tool - maybe it helps. As said, I have not tried that, because I have no iPhone. http://www.iphonediskdrive.com/about/ If you want to go along T...

Couldn't explicit code page selection be expanded also on non-CP encodings, i.e. UTF-8, UTF-16, ...? Why? Are there files with double encoding? Please, take your time and read the following slowly and carefully... You are using an encoding autodetection logic, which, as far as my tests go, checks l...

Given the recent developments, is there still something you like to make a clear statement about? Yes, Borut wants to know: Couldn't explicit code page selection be expanded also on non-CP encodings, i.e. UTF-8, UTF-16, ...? When previewing or raw viewing UTFxx, could you explicitly show the BOM st...

I think also in Raw View of text-type a LF (or combination of CRLF) should be executed. I'm displaying your "ASCII 0 to 255...txt", and it's displayed as only 1 line. Yup, this is exactly what I have also seen, but did not want to be overly pushy. :) But Peter is right: LF should better b...

v10.90.0201 - 2012-03-21 13:48 + Text Preview: Added more codepages to the dropdown menu in the Preview tab and improved the labels. * Raw View | Hex: Now middot instead of dot is used to replace NULLs. * Raw View: Now Unicode (wide) files are shown uninterpreted (byte-wise) in the non-hex view. NU...

admin wrote:What about middot? It looks good (and the text is well readable) and it does not merge with the normal and quite common dot.

Yes, probably better then dot, I agree.

admin wrote:Add the ability to show binary files in non-hex-view? Maybe, not sure.

Why restrict, unless there are some programming pitfalls?

For normal text containing "strange" codes the square is better. For double byte character sets surely the dot is better. My opinion: In Preview: Always box, when for any reason a code point is not representable. In Raw View: Always dot, when octet in ctrl-area (up to CRLF and the like fe...

Previewing "l.dat" in CP 1252 will, display the a-umlaut as a double quote of sorts, but Lübeck will be displayed as Lbeck and the u-umlaut seems to have vanished completely. My default CP is apparently 1250 and I see ü as a narrow box (as far as I can judge). Suggestion to Don: For stand...

Hi Don, I have made a few simple tests with files encoded in UTF-8 and UTF-16LEwBOM (I am enclosing them here, in case anyone else is interested) and am quite impressed with the result. XY got more useful once more. Now, here are but a few observations/questions/suggestions: Obviously the autodetect...

The usual replacement for such and other control characters that can't be displayed is a sort of rectangle [] character. "If a font is chosen which does not contain a glyph for a codepoint used in the document, typically a question mark ("?"), a box, or some other Substitute characte...

I think it would be very helpful, if we could display such text-files containing some non-displayable characters, be they 00 or else, quite normal as text, where those characters are replaced by some substitution to show "illegal character". +1 (or at least flag somewhere, that illegal ch...