Gogorender uses a (simplistic) algorithm to determine which characters to render. The options panel contains a field for excluding specific character ranges.
Additionally, there are two algorithms. The default is word-by-word rendering, the other (enabled in the options panel) renders entire paragraphs (which is useful for scripts written right-to-left). Tim. On Mar 20 at 07:32 -0700, Arno den Hartog wrote: > How do I tell Gogorender that piece of text needs to be rendered? > Does it only work automatically for foreign languages and LaTeX? > > On Monday, August 6, 2012 2:42:25 PM UTC+2, Timothy Bourke wrote: > > On Aug 6 at 12:47 +0200, Peter Bienstman wrote: > > On Sunday, August 05, 2012 03:37:19 PM [email protected] wrote: > > > mnemododo works wonderfully, but I use it to study Chinese. Chinese > > > characters are rendered too small and poorly shaped with the default > > > android font. Would it be possible to build into mnemododo to set a > custom > > > font just for the app, rather than rooting and switching for the > entire > > > phone? > > > > I believe Tim's gogorender plugin should do the trick: > > > > http://mnemosyne-proj.org/plugins/gogorender > > Peter's right. Gogorender is one possible solution. It's main > advantage is that it can use any font installed on your computer, > without requiring that it be also installed on your phone (it also > uses Qt's excellent font rendering routines). It's main disadvantage > is that word wrap doesn't always work very well. > > Another possibility is to change the Mnemododo font size setting to > "Very Large". > > Alternatively, Mnemododo tries to respect the card type formatting > options chosen within Mnemosyne. It may not be able to match the font, > but it should be able to match colours, sizes, and styles. > > Yet another possibility is to add a file called STYLE.CSS to the > exported cards directory, and then to add css styling for the > exported cards, e.g.: > > div.Mandarin { > font-size: 400%; > } > > Where 'Mandarin' is a tag name with any spaces replaced by > underscores. The exported cards also have "div#q" for the question > field, "div#a" for the answer field, and the field names from the card > types, e.g., "div.f" for the foreign word and "div.m_1" for the > meaning (thanks to Peter's Mnemosyne libraries). It may help to open > the CARDS file (read-only!) in a text editor. > > If none of these work, I could think about porting the gogostyle > plugin to 2.x: > http://www.mnemosyne-proj.org/old/content/gogostyle > It added special tags around sequences of non-latin characters, so > that they could be styled using the STYLE.CSS mechanism. > > Tim. > > > -- > You received this message because you are subscribed to the Google Groups > "mnemosyne-proj-users" 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]. > To view this discussion on the web visit https://groups.google.com/d/msg/ > mnemosyne-proj-users/-/A6tucULmo7gJ. > For more options, visit https://groups.google.com/groups/opt_out. > >
signature.asc
Description: Digital signature
