Thanks, this was really helpful, as the official documentation didn't 
mention this at all. I was trying to use a standard text/vnd.tiddlywiki 
tiddler with the contents *[img[./images/favicon.ico]]* to display the 
favicon, and couldn't work out why it wasn't working properly even when I 
changed it to an image/x-icon type. In the official TW5 documentation, 
neither Setting a favicon <http://tiddlywiki.com/#Setting%20a%20favicon> 
nor ContentType <http://tiddlywiki.com/#ContentType> mention converting to 
base64 at all. I would update the documentation myself, except that it 
currently requires a pull request with GitHub to do that, and that's not a 
skill I have mastered yet.

On Wednesday, April 15, 2015 at 10:02:27 PM UTC+12, Backslash wrote:
>
> Hi,
> just to enhance documentation after spending some hours to understand how 
> favicon works.
> In this tiddler:
> http://tiddlywiki.com/#Setting%20a%20favicon
> You could add following lines to explain better how to add a favicon 
> (tested on chrome 42 and firefox 37 on linux platform):
>
> Already formatted for tiddliwiki
>
>
> * Search for favicon in search bar on right side and open or create 
> $:/favicon.ico
> * convert your image (16x16) in base64, in linux just type in cli:
> ```
> your_image_filename.ico base64 > favicon.txt
> ```
>
> * again in tiddler $:/favicon.ico in plaintext first copy the content of 
> favicon.txt (the base64 img) and then set the content type to "ico format 
> icon file image/x-icon)
> *save
>
>
> best regards 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/22f057e4-f083-4a82-9473-f14a56fde2fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to