http://julien.danjou.info/blog/index.php/ Julien Danjou's blog fr Mon, 25 Aug 2008 15:52:39 +0200 All Right Reserved http://blogs.law.harvard.edu/tech/rss Dotclear http://julien.danjou.info/blog/index.php/post/2008/04/27/Extending-pango-markup-attributes#c135720 urn:md5:352a9d1b34a8641641b2c4405acd4e2f Tue, 01 Jul 2008 08:37:58 +0200 jd <p>I finally managed to do it using GMarkup API. <img src="/blog//themes/geeek.org/smilies/smile.png" alt=":-)" class="smiley" /></p> http://julien.danjou.info/blog/index.php/post/2008/04/27/Extending-pango-markup-attributes#c135718 urn:md5:597aa57620b663c5385c9a6b32e84d48 Tue, 01 Jul 2008 01:38:06 +0200 Puneet Madaan <p>you can create your own parser... GMarkUp is nothing more then a parser, which is feeding Attributes and layout to Pango rendering engine...<br /> Try this link to understand Pango interaction.</p> <p><a href="http://www.gnu.org/software/guile-gnome/docs/gdk/html/Pango-Interaction.html#Pango-Interaction" title="http://www.gnu.org/software/guile-gnome/docs/gdk/html/Pango-Interaction.html#Pango-Interaction" rel="nofollow">http://www.gnu.org/software/guile-g...</a></p> <p>Beside this if you are using it for some project on PC.. give a try to ANTLR, that might be better for parsing, and can generate C++ code too</p> <p>In case, if you are on embedded platform... then our old friend, the lex and yacc is recommended, rather then hand written parsers for extensibility reasons...</p> <p>in-fact majority of parsers are already existing, so you only need to work around the rendering codes...</p> <p>Greetings</p>