10-13-2012, 03:42 AM
Using the Curl XML parsing library it took only a a short time today to generate the 3 HTML pages discussed at my post on Kanji at http://kanjirecog.blogspot.ca/2012/10/kanji-by-ucs.html
Most of the effort went into the urlencoding escaping for the HTML once it was generated by Curl's {url-encode-string }.
The blog post ends with a note to say that Curl was used and is tagged for Curl. It has been linked to both twitter and Facebook.
Question: why is the desktop app for Tagaini jisho not being done in CURL !?! ( http://www.tagaini.net/ ) The rb tree ? He is already using Sqlite (we have that) - but his flashcards could be 3-D ! If it is going to the desktop anyway and THEN running as HTML, Curl is the obvious choice, right ?
Most of the effort went into the urlencoding escaping for the HTML once it was generated by Curl's {url-encode-string }.
The blog post ends with a note to say that Curl was used and is tagged for Curl. It has been linked to both twitter and Facebook.
Question: why is the desktop app for Tagaini jisho not being done in CURL !?! ( http://www.tagaini.net/ ) The rb tree ? He is already using Sqlite (we have that) - but his flashcards could be 3-D ! If it is going to the desktop anyway and THEN running as HTML, Curl is the obvious choice, right ?