If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
"Fokke Nauta" wrote
| That's really weird indeed. I imagine Irfan Skildjan is just trying to be thorough in internationalizing his software. And if he has to us unicode for one language it's probably easier to use it for all. But I don't know. | Perhaps an hex editor will show what's in it | as Paul suggested? | Yes. That's how I know. I downloaded the latest version. Open it in something like HxD and you can see the actual bytes. Normally, Notepad should show the same text regardless of encoding, but unicode is very different from ANSI in terms of the actual bytes. |
Ads |
#17
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 17/06/2018 16:53, Mayayana wrote:
"Fokke Nauta" wrote | That's really weird indeed. I imagine Irfan Skildjan is just trying to be thorough in internationalizing his software. And if he has to us unicode for one language it's probably easier to use it for all. But I don't know. | Perhaps an hex editor will show what's in it | as Paul suggested? | Yes. That's how I know. I downloaded the latest version. Open it in something like HxD and you can see the actual bytes. Normally, Notepad should show the same text regardless of encoding, but unicode is very different from ANSI in terms of the actual bytes. That's interesting! I have HxD installed and will give it a try. I'll be back on this! Fokke |
#18
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
In article
malone wrote: I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Using Windows 8 and earlier this was easy. Just open it with Notepad, make the edits if necessary, save and close it and everything works fine. Things are a bit different using Windows 10. Opening the i_view64.ini file one sees a mass of what look like Chinese characters. Despite the font being set at Consolas Regular which is the default for Notepad. Opening the i_view64.ini file created on the Windows 10 machine on a Windows 8 machine and it's all Chinese Opening the i_view64.ini file created on the Windows 8 machine on a Windows 10 machine and it's all ok. Both computers are using the most recent version of Irfanview (4.51 64 bit). Winver 1709 Can anyone explain this rather strange behaviour? And, even, could anyone using Irfanview with Windows 10 have a quick look and see whether you can read the .ini file opened with notepad? Malware. |
#19
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
malone schreef op 15-06-2018
in : I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Use Notepad++ -- MdW. |
#20
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 19 Jun 2018, Machiel de Wit
wrote in alt.comp.os.windows-10: malone schreef op 15-06-2018 in : I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Use Notepad++ I don't think that's the real solution. Notepad++ should read it (and it does for me) but so should Windows Notepad (and it does for me.) |
#21
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
Nil wrote:
On 19 Jun 2018, Machiel de Wit wrote in alt.comp.os.windows-10: malone schreef op 15-06-2018 in : I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Use Notepad++ I don't think that's the real solution. Notepad++ is always the right solution |
#22
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 20-Jun-2018 2:23 pm, Nil wrote:
On 19 Jun 2018, Machiel de wrote in alt.comp.os.windows-10: malone schreef op 15-06-2018 : I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Use Notepad++ I don't think that's the real solution. Notepad++ should read it (and it does for me) but so should Windows Notepad (and it does for me.) As the OP, my conclusion so far is that it's got nothing to do with the text reader; Notepad, Notepad++, Wordpad and others are all consistent. And, I'm now not too sure how important the Windows 10 aspect is as a second Windows 10 computer doesn't show this behaviour. It appears to me that on this one Windows 10 machine Irfanview is generating an .ini file subtly different from that created by all the other computers. And this subtle difference is reflected in every other line appearing to be Chinese. Some corruption of the line-feed / para feed code? As this appears to be a unique problem with my computer, rather than a generic issue, I expect it isn't really appropriate for this newsgroup. I haven't got a hex reader and I'm not too sure whether I have the expertise to interpret the output. But, for anyone who's still interested I have put the two files here https://www.dropbox.com/s/76bux1x0wi...64_W8.ini?dl=0 (.ini file created by Irfanview on a Windows 8 machine) and here https://www.dropbox.com/s/3hpgu1fgxs...4_W10.ini?dl=0 (.ini file created by Irfanview on the misbehaving Windows 10 machine) And, when I've a moment I'll reinstall Irfanview..... |
#23
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
malone wrote:
On 20-Jun-2018 2:23 pm, Nil wrote: On 19 Jun 2018, Machiel de wrote in alt.comp.os.windows-10: malone schreef op 15-06-2018 : I use Irfanview a lot and sometimes I need to view or edit the i_view.ini file. Use Notepad++ I don't think that's the real solution. Notepad++ should read it (and it does for me) but so should Windows Notepad (and it does for me.) As the OP, my conclusion so far is that it's got nothing to do with the text reader; Notepad, Notepad++, Wordpad and others are all consistent. And, I'm now not too sure how important the Windows 10 aspect is as a second Windows 10 computer doesn't show this behaviour. It appears to me that on this one Windows 10 machine Irfanview is generating an .ini file subtly different from that created by all the other computers. And this subtle difference is reflected in every other line appearing to be Chinese. Some corruption of the line-feed / para feed code? As this appears to be a unique problem with my computer, rather than a generic issue, I expect it isn't really appropriate for this newsgroup. I haven't got a hex reader and I'm not too sure whether I have the expertise to interpret the output. But, for anyone who's still interested I have put the two files here https://www.dropbox.com/s/76bux1x0wi...64_W8.ini?dl=0 (.ini file created by Irfanview on a Windows 8 machine) and here https://www.dropbox.com/s/3hpgu1fgxs...4_W10.ini?dl=0 (.ini file created by Irfanview on the misbehaving Windows 10 machine) And, when I've a moment I'll reinstall Irfanview..... Is the i_view64_W10.ini in its original form ? It looks like you've edited it and added a line to the top ??? Try uploading the i_view64_W10.ini again, with no edits at all to it, so the BOM won't be modified. One thing I notice, is there is something passing strange going on with some 0D 00 0D 0A 00 0D sequences. It looks like something is *trying* to apply carriage returns and/or line feeds in a non-Unicode way. Did you use a non Unicode editor, to edit the file ? Maybe the file was edited by Win98 Notepad ? :-) Paul |
#24
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
"Chris" wrote
| Notepad++ is always the right solution I like it for dealing with extremely large files. It's clean, dependable and well built. But aside from opening 2 MB files quickly, it's little more than an overproduced version of Notepad, using 3 times the RAM. The color coding isn't specific enough to be worth having. None of it is actually specific to any coding language. So it's mostly just a really good version of a text editor. But since text is "just text", Notepad++ is rarely any more useful than Notepad. Personally I use Notepad far more than anything else. I often have a few instances open with text snippets. I jot down URLs or phone numbers. I save webpages as text by copying/pasting into Notepad. Notepad++ doesn't even provide an SDI mode. (One window for each file.) It has 3 options for multi-instance window and they all give me a single window with tabs. I can hide the tab bar, but that also doesn't give me SDI windows! |
#25
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
"malone" wrote
| https://www.dropbox.com/s/3hpgu1fgxs...4_W10.ini?dl=0 (.ini | file created by Irfanview on the misbehaving Windows 10 machine) What a mess. It looks like maybe you tried to edit it with a program that didn't recognize unicode properly. Or maybe you accidentally saved it as ANSI? Or maybe you tried to edit it in a complex editor like Word and that misinterpreted characters? The reason I say that is because, in addition to the glitch with returns that Paul mentioned, part of the file is actually ANSI. It's just not visible when the file is opened as unicode. Starting with [WinPosition] it turns to ANSI. That made me think that a special-use editor that sees [ as a key character might be able to do the damage I see. Maybe try just deleting it. IV should create a new copy. Also, for what it's worth: Dropbox URLs that end with "dl=0" can be turned into direct file links by switching it to "dl=1". dl stands for "download". With dl=0 you have to load the webpage and must have script enabled. With dl=1 you get a download dialogue directly. |
#26
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
Chris wrote:
[...] Notepad++ is always the right solution Notepad[++] is for WIMPs. Real Men (TM) use vi[m](1)! |
#27
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 20 Jun 2018 14:46:26 GMT, Frank Slootweg
wrote: Chris wrote: [...] Notepad++ is always the right solution Notepad[++] is for WIMPs. Real Men (TM) use vi[m](1)! WIMP - Windows Interface with Mouse Pointer? Windows Interface Manipulation Program? |
#28
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
In article , Char Jackson
wrote: Notepad++ is always the right solution Notepad[++] is for WIMPs. Real Men (TM) use vi[m](1)! WIMP - Windows Interface with Mouse Pointer? Windows Interface Manipulation Program? windows, icons, menus, pointer, usually used in a derogatory context, as above. https://en.wikipedia.org/wiki/WIMP_(computing) |
#29
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 20 Jun 2018, Chris wrote in
alt.comp.os.windows-10: Nil wrote: I don't think that's the real solution. Notepad++ is always the right solution You may have a point there! |
#30
|
|||
|
|||
Reading an .ini file with Notepad using Windows 10
On 20 Jun 2018, "Mayayana" wrote in
alt.comp.os.windows-10: I like it for dealing with extremely large files. It's clean, dependable and well built. But aside from opening 2 MB files quickly, it's little more than an overproduced version of Notepad, using 3 times the RAM. That's an odd description. It has dozen's of useful features that Notepad would never dream of having. Just because you don't use them doesn't mean it's "over produced". The color coding isn't specific enough to be worth having. It's as specific as you tell it to be. None of it is actually specific to any coding language. It is if you tell it to be. So it's mostly just a really good version of a text editor. But since text is "just text", Notepad++ is rarely any more useful than Notepad. It is to me. Notepad++ doesn't even provide an SDI mode. (One window for each file.) Good! If it did have that feature it would be overproduced. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|