NFO Viewer for Linux?
Well I was googling for NFO viewers for Linux, and I found absolutely nothing. In short anyone know of one for Linux?
|
whats wrong with a normal text editor?
|
Quote:
|
i dont see what you mean - if you just mean putting characters in shapes to have pictures, then like pico and gedit work fine for me...
|
Gedit should work fine have to make sure word wrap is on
|
They all seem to. Kwrite does, Jed seems to, Nano seems to, Xedit does. I am sure that Nedit will too. Lotsa choices.
|
None of the suggested alternatives show ASCII art. What I am looking for (and probably the thread starter too) is an application that shows the .nfo files like windows notepad with terminal used as font.
this is how i want it to look: http://www.nforce.nl/nfos/renderer/l...k.php?id=82241 (just an example...) /s1k |
VI seems to do the trick, but I don't know if that's exactly what you're looking for.
Billspork |
No it doesn't look right in VI, same as all the other viewers i have tried. Any other suggestions?
|
hi guys
i have a solution :) just select a fixed sized font in aterm to show ascii properly. i use this font : in my .Xresources : aterm*font:-dosemu-vga-medium-r-normal-*-*-160-*-*-p-*-ibm-cp437 and a user in #linuxger (ircnet) told me it would also work to change to cp437 but i didnt test it yet. hope this helps some of you. greets mephist0 |
i have written a little bash script to view .nfo files properly :
#!/bin/sh consolechars -m cp437 cat $1 consolechars -m iso01 just copy to /usr/bin and type: nfo <dir.file.nfo> and youre done :) greetz mephist0 |
Solution with gvim
Hey thanks mephist0666 for the solution w/ consolechars,
but I don't have consolechars on my gentoo box.. If you open the .nfo file with gvim, and then type: :set encoding=8bit-437 it will switch to a character set appropriate for ascii art. Then do a : :set encoding=latin1 to switch back to normal (or whatever your default set up is) Anybody knows how to script the .vimrc file to tell it that if the file extension is .nfo then switch encoding to 8bit-437 ? - Guillaume. |
the suggestions above are a little complicated for me but through wine an .nfo viewer called jane displays the art perfectly. here is a sample of what jane can do
here is the jane website = http://www.kifoth.de/jane/html/download.php |
I wrote a simple nfo viewer in Python using GTK2.
To try it: 1. Install packages Python and PyGTK if you don't have them already. 2. Get the Lucida Console P font monospace works as well, but it's not as good. 3. Download my script http://koti.mbnet.fi/~ots/scripts/nfoview Put it for example in ~/bin or some place that's in your PATH and give it execute permissions. Edit the settings at the start of the file if needed. 4. Use it Code:
nfoview file.nfo |
ow50,
works great .. thx |
nfoview by ow50 is not there? where can I get it?
|
An NFO Viewer written in Java (jnfoviewer) is available at:
http://www.dsnine.co.uk/~gary/projects/nfoviewer/ It has a few issues at the moment which are listed on the web page. But once they are resolved it should provide a cross platform way to view NFO files. |
Quote:
|
my 2 cents
just to give my 2 cents, here's how i got my setup working.
i should point out that my objective was to incorporate nfo viewing capabilities to my current text editor (ie. Kate)... not having a separate application just to look at nfo files :p so its pretty simple... 1. download and install the Lucida Console font as mentioned earlier. 2. in Kate, open up the conf (Settings->Configure Kate...), go to Editor->Fonts & Colors and hit the New button. 3. give a name to your new scheme... (maybe "NFO" ? :D) 4. now you can customize the look and feel of your nfo... bgcolor, fgcolor... etc. just play with it however you want, the only thing important is to make sure to change the font (in the font tab) to our newly installed Lucida Console font. 5. hit the Apply button at the bottom of the screen. 6. now go to the Editor->Filetypes section and hit the New button. 7. in the name section well.. you put a name (maybe "NFO" ? :D) 8. in the variables section you put kate: scheme NFO; encoding ibm866; (here you should change "NFO" to the name you gave to your scheme on step 3) 9. in the File extensions section you put *.nfo 10. hit OK, restart Kate and open your NFO. VOILA! i know most people say that you need cp437 encoding to get this working (which Kate doesn't have) but i found out that the ibm866 is pretty close if not identical to cp437 when used with the Lucida Console font. hope that will be helpful to someone out there! :cool: cheers! |
Google Resurrection
Although my first post here will be a serious resurrection, i’d like to note that this thread (page) is still #1 result for most relevant terms on google.
my correction to the above solution: kate does support cp437 now, so instead of changing the font, a simple “kate: encoding cp437;” is sufficient. whole remaining procedure (shamelessly copied and edited from above):
|
Why not run iconv -f cp437 filename.nfo > fixed-filename.txt and be done with it?
Nominal Animal |
because it will work with every new .nfo file you get, without having to fire a conversion program each time.
|
All times are GMT -5. The time now is 06:20 AM. |