for local files ( "text/something" ) goto File >
Open File .
For remote files?
In the search bar , type the remote location of
that file and press enter.
And then I get the choice of saving to disk or opening in another
application. How do I configure Firefox to open that kind of file in
the browser window itself? In Opera, you can choose "open in Opera".
in "opening in another application" click on
'browse' , select Firefox and also check the
'remember' option in the window.
> >>>> Bob T. wrote:
> >>>>> Is it possible to configure Firefox to open text/something files in the
> >>>>> current Firefox display, rather than in another application?
> > And then I get the choice of saving to disk or opening in another
> > application. How do I configure Firefox to open that kind of file in
> > the browser window itself? In Opera, you can choose "open in Opera".
> >
>
> in "opening in another application" click on
> 'browse' , select Firefox and also check the
> 'remember' option in the window.
It doesn't work (at least, it doesn't on Linux). Firefox goes into an
infinte tab-opening loop.
first , goto Tools>Options>Downloads>View & Edit
Actions. search for that file extension. can you
find any such file extension there?
what type of file you are trying to open?
On Linux, the path is
Edit | Preferences | Downloads | View & Edit Actions
and there are no such file extensions there (.c, .tex, .sty, etc. are
what I'm trying to display in the
browser window).
A text file. But unless you're running FF on linux, you won't be
able to help him. It sounds like it's a problem limited to the
Linux versions. On Win platforms FF opens text files seamlessly.
--
}:-) Christopher Jahn
{:-( http://home.comcast.net/~xjahn/Main.html
Any cat that behaves like a dog is welcome in my universe.
(Jonathan Carroll)
sorry , .c , .tex , .sty files are not supported
under Firefox .
"infinite tab-opening loop."-
Actually "you are deliberately forcing Firefox to
do something that it is clearly not
suitable for " : see this link :
https://bugzilla.mozilla.org/show_bug.cgi?id=218637
you should open those file extensions in their
editor, although .txt file can be opened under
Firefox ( Linux version )
I'm using Fedora core and .txt file can be opened
under Linux without any problem. But some other
types of file can't be opened under Linux like (
.doc , .c etc. ). see my another post in this thread
> > what type of file you are trying to open?
>
> A text file. But unless you're running FF on linux, you won't be
> able to help him. It sounds like it's a problem limited to the
> Linux versions. On Win platforms FF opens text files seamlessly.
It's not so simple. It depends on what the server decides to put into
the header. Obviously text/html works as expected in Linux and I
believe text/plain does too. But mime types like text/x-csrc and
text/x-tex don't. Because I can't change what servers do, I want to
configure the browser to do what I want it to do. It seems this isn't
possible in Firefox.
Here is a list of mime types that are internally
supported by Firefox
text/css Handled Internally
text/ecmascript Handled Internally
text/html Handled Internally
text/javascript Handled Internally
text/plain Handled Internally
text/rdf Handled Internally
> Here is a list of mime types that are internally
> supported by Firefox
> text/css Handled Internally
> text/ecmascript Handled Internally
> text/html Handled Internally
> text/javascript Handled Internally
> text/plain Handled Internally
> text/rdf Handled Internally
>
> [http://plugindoc.mozdev.org/winmime.html]
There's no reason that I can see why I shouldn't be able to configure a
browser to treat *any* text file as text. What could be easier or more
secure? I guess I'll submit a feature request.
>
> Nir wrote:
>
>> Here is a list of mime types that are internally
>> supported by Firefox
>> text/css Handled Internally
>> text/ecmascript Handled Internally
>> text/html Handled Internally
>> text/javascript Handled Internally
>> text/plain Handled Internally
>> text/rdf Handled Internally
>>
>> [http://plugindoc.mozdev.org/winmime.html]
>
> There's no reason that I can see why I shouldn't be able to
> configure a browser to treat *any* text file as text.
The server *should* be set to serve the files *properly*. That's
the entire point of having the server "serve" a mime filetype -
so that your browser will know how to handle the file.
Rather than break the browser or overturn its proper function,
get webmasters to clean up their pages.
--
}:-) Christopher Jahn
{:-( http://home.comcast.net/~xjahn/Main.html
One billion Chinese can't be Wong.
> > There's no reason that I can see why I shouldn't be able to
> > configure a browser to treat *any* text file as text.
>
> The server *should* be set to serve the files *properly*. That's
> the entire point of having the server "serve" a mime filetype -
> so that your browser will know how to handle the file.
>
> Rather than break the browser or overturn its proper function,
> get webmasters to clean up their pages.
The server *is* doing it properly: it's the browser that refuses to
display, say, text/x-csrc
or text/x-tex files as text.
Files of type: text/x-tex are not plain/text files but are those generated
by a word processor such as LaTex and can require the viewing system to
have Postscript Type 1 fonts installed.
--
Ron K.
Don't be a fonted, it's just type casting.
> > The server *is* doing it properly: it's the browser that refuses to
> > display, say, text/x-csrc
> > or text/x-tex files as text.
> >
>
> Files of type: text/x-tex are not plain/text files but are those generated
> by a word processor such as LaTex and can require the viewing system to
> have Postscript Type 1 fonts installed.
You're wrong. text/x-tex files are ASCII text files that can be
processed by
LaTeX or edited in any text editor, just as text/x-csrc files are text
files that can
be processed by a C compiler or edited in a text editor.
It extends the "Open With/Save to Disk" dialog with "Open In browser"
(unfortunately it doesn't allow you to select "Do this automatically for
files like this from now on").
--
Regards,
Roland
> > Is it possible to configure Firefox to open text/something files in the
> > current Firefox display, rather than in another application?
> The "Open In Browser" extension is probably what you want/could use.
> <http://www.spasche.net/mozilla/>
>
> It extends the "Open With/Save to Disk" dialog with "Open In browser"
Thanks. Unfortunately it doesn't work for me. After selecting Open in
browser as text, the same dialog re-appears. Perhaps my mimeTypes.rdf
is screwed up by my attempts to hack it.
Then WHY not save them as .txt files, if that's what they are?
Hm?
--
}:-) Christopher Jahn
{:-( http://home.comcast.net/~xjahn/Main.html
If you drink carrot juice for a hundred years, you will live for
a long time.
BTW, the correct mimetype for .tex files is application/x-tex
And guess what? It's not a text file.
http://www.latex-project.org/guides/
--
}:-) Christopher Jahn
{:-( http://home.comcast.net/~xjahn/Main.html
Which caused little rhythmic darts of red to pulsate gently in
the morning sun.
> Is it possible to configure Firefox to open text/something files
> in the current Firefox display, rather than in another
> application?
In the location bar, you could type view-source: in front of the URI
for the file. I looked for an extension that would put the option in
the link's context menu, but a quick search didn't turn anything up.
The only way I can think of to do it automagically, presuming the
filenames have extensions, is to write a greasemonkey script which
would change the URLs for them, adding the "view-source:".
--
»Q«
> "Bob T." <rdte...@gmail.com> wrote in
> news:1157234642.4...@p79g2000cwp.googlegroups.com:
>
>> Ron K. wrote:
>>
>>>> The server *is* doing it properly: it's the browser that
>>>> refuses to display, say, text/x-csrc
>>>> or text/x-tex files as text.
>>>
>>> Files of type: text/x-tex are not plain/text files but are
>>> those generated by a word processor such as LaTex and can
>>> require the viewing system to have Postscript Type 1 fonts
>>> installed.
>>
>> You're wrong. text/x-tex files are ASCII text files that can
>> be processed by
>> LaTeX or edited in any text editor, just as text/x-csrc files
>> are text files that can
>> be processed by a C compiler or edited in a text editor.
>
> BTW, the correct mimetype for .tex files is application/x-tex
> And guess what? It's not a text file.
>
> http://www.latex-project.org/guides/
application/x-tex is the right MIME type, but .tex files are indeed
just ASCII text files. They are input files for LaTeX. There's a
very simple example .tex file in the second grey box at
<http://www.latex-project.org/intro.html>.
--
»Q«
--
Peeves That Your Dog Has About You . . . A Message From Your Dog:
Any haircut that involves bows or ribbons. Now you know why we chew
your stuff up when you're not home.
The sleight of hand, fake fetch throw. You fooled a dog! Whoooo
hoooooooo! What a proud moment for the top of the food chain.
Taking me to the vet for "the big snip", then acting surprised when I
freak out every time we go back!
. . . to be continued
Roland
--
Peeves That Your Dog Has About You . . . A Message From Your Dog:
Getting upset when I sniff the crotches of your guests. Sorry, but I
haven't quite mastered that handshake thing yet.
Dog sweaters. Hello??? Haven't you noticed the fur?
Acting disgusted when I lick myself. Look, we both know the truth.
You're just jealous.
Now lay off me on some of these things! We both know who's boss here!
You don't see me picking up your poop do you???
But any other site showing a directory listing with C source files
should do, e.g. <http://www.scaramanga.co.uk/stuff/c-code/>
Otherwise Google for <http://www.google.com/search?q=%22text/x-csrc%22>.
--
Regards,
Roland
Because they're at remote sites. They're not my files.
And where at that site does it say that .tex files are not text files?
The first Contributed documentation reference is to
http://www.techscribe.co.uk/ta/latex-introduction.pdf
which says:
"Unlike WYSIWYG tools such as FrameMaker and Word, it uses plain text
files that contain formatting commands."
application/x-tex or text/x-tex are both legitimate, reflecting the
fact that a .tex can be either edited by a text editor or processed by
a tex system, just as an html file can be either edited or rendered by
a browser.
I've been using TeX for about 20 years so I think I know something
about it. If you're not interested, I couldn't care less. Thanks for
your attempts to help. Unfortunately, the problem is with Firefox,
not, as I'd hoped, with configuration.
> > The server *is* doing it properly: it's the browser that refuses to
> > display, say, text/x-csrc
> > or text/x-tex files as text.
> >
> then can you provide a link to a site where you're having this problem.
CTAN has hundreds of .tex files; for example:
http://www.ctan.org/tex-archive/graphics/prerex
and there are C files in the src sub-directory. Notice that the
Makefile in the src directory *is* rendered as text, whereas the .c and
.h files are not.