For all people interested in using breve with utf-8 (or ascii), you
may download a unicode version of brevé here:
<http://www.maths.lth.se/~olivier/download/breve-unicode.zip>
The difference with the standard brevé is that it allows you to have
all your strings encoded in utf-8 (and ascii of course). For example:
div["你好吗? ▸ ", em["я не понимаю"], "▸ 3 km²"]
Besides the django helper is much improved, allowing to pass brevé
settings via a BREVE_OPTS dictionary in the "settings.py" file.
Hope this helps!
== Olivier
This is true :P I've been busy.
> For all people interested in using breve with utf-8 (or ascii), you
> may download a unicode version of brevé here:
> <http://www.maths.lth.se/~olivier/download/breve-unicode.zip>
>
> The difference with the standard brevé is that it allows you to have
> all your strings encoded in utf-8 (and ascii of course). For example:
> div["你好吗? ▸ ", em["я не понимаю"], "▸ 3 km²"]
>
> Besides the django helper is much improved, allowing to pass brevé
> settings via a BREVE_OPTS dictionary in the "settings.py" file.
I'll try to make some time to review your changes and if it all looks
good, get them integrated. It might not be until this weekend though.
> Hope this helps!
It does.
Cliff
I installed this version on a site to test and it broke decoding
something :P I've regressed CVS back to the last working 1.1.7 snapshot
and am going to try to get this to work (although I'm not going to
hard-code utf-8 in, rather a configuration variable).
I'm going to try and devote a bit more time to Breve than I have been
for the last couple of months. Getting rusty isn't progress =)
Cliff
On Nov 9, 11:15 am, Cliff Wells <cl...@twisty-industries.com> wrote:
> On Tue, 2007-11-06 at 01:46 -0800, Olivier wrote:
> > Things are not going very fast around here. :-)
>
> > For all people interested in using breve with utf-8 (or ascii), you
> > may download a unicode version of brevé here:
> > <http://www.maths.lth.se/~olivier/download/breve-unicode.zip>
>
> > The difference with the standard brevé is that it allows you to have
> > all your strings encoded in utf-8 (and ascii of course). For example:
> > div["你好吗? ▸ ", em["я не понимаю"], "▸ 3 km²"]
>
> I installed this version on a site to test and it broke decoding
> something :P
It is possible. My patch only works with regular strings encoded in
utf-8 (or ascii, obviously). Anything else will cause an error.
> I've regressed CVS back to the last working 1.1.7 snapshot
> and am going to try to get this to work (although I'm not going to
> hard-code utf-8 in, rather a configuration variable).
I'm not sure that this is such a good idea. There is no good reason to
use another encoding than utf-8. Utf-8 is ascii compatible, covers all
the possible languages and all possible symbols. Any document in any
encoding may be converted to utf-8 (but not the opposite, of course).
All in all, there is little reason to use any another encoding. But
that's just my two ¢.
I'd be very grateful if those changes were incorporated to brevé. You
will also have to change the unicode example in svn. All strings have
to be regular strings, as in my example above.
Thanks!