Beoardielingen foar Markdown Viewer Webext
Markdown Viewer Webext troch Cimbali
100 beoardielingen
- Wurdearring: 5 fan 5troch conorj, 7 jierren lynWorks fine for file opened locally - raw markdown is displayed initially and upon clicking icon it is rendered correctly.
- Wurdearring: 5 fan 5troch Firefox-brûker 12813342, 7 jierren lynIf firefox does not correctly assume that your files are UTF-8 encoded, a possible solution (besides using a Byte Order Marker in your file, which is annoying for several reasons) is the following:
go to about:config and set the intl.charset.fallback.utf8_for_file variable to true. That worked for me.
This is related to the following bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1071816Antwurd ûntwikkeler
7 jierren lyn pleatstThank you for the feedback and for this tip! I have added it to the README, and the README is linked from the add-on options page. - Wurdearring: 5 fan 5troch Firefox-brûker 13899646, 7 jierren lynNote that the author notes that the extension only works "if the content is plain text". That means your browser needs to be rendering the file in a tab already, just without rendering the markdown elements. If it's downloading it instead, the suggestion from 7cac17 below, to add a MIME type for markdown files, worked for me (I'm also on Ubuntu).
- Wurdearring: 5 fan 5troch Firefox-brûker 13008505, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 13811014, 7 jierren lynMarkdown that is super effective. Don't know why it is receiving negative reviews.
- Wurdearring: 1 fan 5troch Firefox-brûker 13809707, 7 jierren lynDoes not work at all for me with local markdown files. The effect is that a popup comes up asking what to do with the file, and when selecting "Open in FF" it opens a new tab and brings up the same popup again. Using FF 52.6.0 on RHEL 7.4. I did not try markdown files from a HTTP server.
Antwurd ûntwikkeler
7 jierren lyn pleatstThis is the most common user issue on the project in GitHub. I've now explained in the README file why a BOM is important and supplied workarounds, including setting intl.charset.fallback.utf8_for_file to true, which tells Firefox to assume UTF-8 for local files. You the user have to do this step; the add-on has no way to configure settings. Fortunately, it's really very very easy!- Wurdearring: 5 fan 5troch Firefox-brûker 13801131, 7 jierren lynNice add-on, woks fine for me. Maybe just missing the rendering of [TOC] tag.
- Wurdearring: 5 fan 5troch Firefox-brûker 13798972, 7 jierren lynFor people who found FF keeps asking "what app should be used to open the markdown file", just check the solution (at least for Ubuntu) here: https://github.com/KeithLRobertson/markdown-viewer/issues/2#issuecomment-321940542
- Wurdearring: 5 fan 5troch Firefox-brûker 13189330, 7 jierren lynUtf8 - encoded Chinese documents display messy code, while GB - encoded Chinese documents display normal. Please fix it. Thank you for sharing this practical extension.
------------------------
The problem has been solved. An option to change the default encoding to UTF-8 in about:config: set the value of intl.charset.fallback.utf8_for_file to true. It is perfect now. - Wurdearring: 5 fan 5troch Firefox-brûker 13628151, 7 jierren lyn
- Wurdearring: 2 fan 5troch Firefox-brûker 13519333, 7 jierren lyn
- Wurdearring: 3 fan 5troch Nobitz, 7 jierren lynNot working with this URL: https://gist.githubusercontent.com/anonymous/6033c7fcb0caf7de6f0eec4637e79756/raw/71a19f13314e0e4af8c0913dd7131465b5910488/ja_en.md
And, it chooses wrong encoding system for Japanese characters. You can also reproduce it with above markdown file.Antwurd ûntwikkeler
7 jierren lyn pleatstYour site gist.githubusercontent.com replies with a CORS header Access-Control-Allow-Origin. Firefox therefore refuses to inject the add-ons scripts into the page, so your markdown never gets rewritten/beatified. If you save the file locally and view that in the browser, it should convert. But since your file is UTF-8 with no BOM, you will need to configure intl.charset.fallback.utf8_for_file to true. Please see the project README file for more details. - Wurdearring: 3 fan 5troch Kelvin Chin, 7 jierren lynIt is a nice and quick add-on, but the only limitation is it looks like not well support non english charater unless encode under utf-8 with bom
Antwurd ûntwikkeler
7 jierren lyn pleatstThank you for the review! There are now solutions for this. Please try the latest version and check out the README file. It explains how to configure a setting which supports local UTF-8 files with no BOM. - Wurdearring: 5 fan 5troch luk3yx, 7 jierren lynThis add-on just works, I can now view markdown files with no additional software.
- Wurdearring: 4 fan 5troch Philipp Bielefeldt, 8 jierren lynIt just displays .md files. Plain and simple – exactly what I searched for (there are MD editors with far more bells and whistles, if you want to, this one is totally minimalist).
Unfortunately, Firefox (at least under openSUSE Linux) has an issue with the MIME type. The solution linked here solves it: https://github.com/KeithLRobertson/markdown-viewer/issues/2
Oh, and btw, it only works (for me) with UTF-16, not UTF-8 as long as you don't manually add it a BOM, which is somewhat unusual … (can be fixed with " sed -i '1s/^/\xef\xbb\xbf/' foo ") - Wurdearring: 5 fan 5troch Firefox-brûker 13314696, 8 jierren lynWorks well. I noticed that "##Some header here" doesn't convert to an , but "## Some header here" does (note the space after the ##). But, at least according to daringfireball, that space *is* required, so...
- Wurdearring: 4 fan 5troch DanBe, 8 jierren lynPresque parfait !
Petits bémols:
1) Il faut remplacer les sauts de ligne Linux (LF) par des sauts de ligne Microsoft (CR/LF).
2) Le rendu HTML est parfois assez différent de ce qu'on obtient avec un convertisseur standard.
Mais le résultat est néanmoins très acceptable.Antwurd ûntwikkeler
8 jierren lyn pleatstThank you for your feedback.
2) This addon uses a standard converter, markdown-it. I think the issue is not the conversion. Probably the Markdown is simply not *styled* the same as you are used to. Version 1.2.0 adds a feature where you can apply custom styling (CSS) for local markdown files; in the future I plan to add a feature to support standardized and custom styling for all markdown files. Eventually.
1) I am not sure what you mean. I was able to view Markdown with Linux (LF) line endings, and they look just the same. Please open an issue on the project in github and describe the problem you are seeing. - Wurdearring: 1 fan 5troch Firefox-brûker 10391247, 8 jierren lynJust remplaced Markdown Viewer on firefox 55.0.3 , OSX.
Does not recognize .md local files. Got FF asking what to do with the file.Antwurd ûntwikkeler
8 jierren lyn pleatstI'm sorry you are unable to use the addon as needed. But I believe the problem is that FF never hands over control of the document to the addon. Check Issue #2 on the github page where there are (links to) configuration steps which have worked on Linux. Perhaps they will work on OSX. Please try them and comment on the issue what steps you took and what happened. Thanks. - Wurdearring: 5 fan 5troch alex_brannson, 8 jierren lynGithub markup renders very well. I'd like to thank the author, it works perfectly for me!
- Wurdearring: 5 fan 5troch Firefox-brûker 13102268, 8 jierren lynI was perfectly satisfied with the older "markdown-viewer" add-on until I found
out it prevented FF's multi-process (aka e10s, electrolysis) feature.
Glad I found "markdown-viewer-webext"! It renders perfectly acceptable, but different, HTML.