[AWFFULL] UTF-8 Fonts, & graphs Was: Re: Announcing AWFFull v3.7.3
Steve McInerney
steve at stedee.id.au
Wed Feb 7 22:52:36 EST 2007
FYI:
have been fiddling around with getting the UTF-8 working in the graphs -
updating graphs.c. This also means a shift to using Truetype - which
isn't a bad thing in any event, just a bit more complex.
Still working on it, but am getting basic success:
http://www.stedee.id.au/files/daily_usage_200605.png
which is an extract with Heveltica Bold ttf for the title. in:
LANG=uk_UA.UTF-8. You'll note the fonts up the side are wrong - haven't
done them yet.
Also tried Swedish, German, and Japanese. All worked, expect the latter,
which I am currently downloading TTF fonts for. Doh!
I've also completed a machine generated translation of several countries
- all I could do with the KDE i18n set.
Ended up using kbabel, and creating a new translation database for each
language. And only a small subset of each full language pack from KDE.
Sheer speed of loading it all in/parsing was a killer.
branches/awffull-3.7.2/po/da.po
branches/awffull-3.7.2/po/el.po
branches/awffull-3.7.2/po/es.po
branches/awffull-3.7.2/po/et.po
branches/awffull-3.7.2/po/it.po
branches/awffull-3.7.2/po/ja.po
branches/awffull-3.7.2/po/nl.po
branches/awffull-3.7.2/po/pl.po
branches/awffull-3.7.2/po/pt.po
Is the raw list of language packs from Subversion. FWIW, those
translations are all marked as fuzzy, and hence won't show up under
normal conditions. It can be overridden by:
rm -f el.gmo && /usr/bin/msgfmt -f --statistics -o el.gmo el.po
style of thing. And then redoing a 'make install' to use the "new" gmo's
instead.
Cheers!
- Steve
on 03/02/07 08:18 Steve McInerney said the following:
> That's a tad frustrating - mainly as it works for me. :-(
>
> Hmm. I just noticed something. All your graphs have come out correctly,
> but the HTML has not.
>
> But for me, the HTML is fine, but the graphs are messed up.
>
> arrrggghhh!
>
> This suggests that we're both getting something right, but not the full
> story. I am surprised to see your graphs looking correct - as I'm pretty
> sure I'm not calling the gd libs correctly to generate UTF-8.
>
> Can I get you to try a few things?
> * Just use the LANG and run that (ie ditch the LANGUAGE)
> This should have zero effect
> * Try a different language. eg ja_JP, or uk_UA are the two I tend to
> test with - they look pretty :-)
> Both with and without the .UTF-8
> * Are you seeing the correct chars if you '-v' the run?, Will only
> generate a small amount of output, but should see some of the different
> characters.
> * This is a long shot, but can you open the output directly vs via the
> webserver (file vs http request)? Any change?
> * Can you:
> iconv --from-code=ISO-8859-1 --to-code=UTF-8
> on the generated HTML output? Does this fix things?
> * What does this give you?
> awffull-3.7.3$ file -i po/*.po
>
> Should be mostly "text/x-po; charset=utf-8", with the occasional us-ascii.
>
> * When you build awffull, what language setting are you using. ie your
> normal default? Not that that seems to make any difference for me. I
> normally work in LANG=C, but switching to LANG=en_AU.UTF-8 made no
> difference.
>
> * ./configure stuff?
>
> checking whether NLS is requested... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for msgmerge... /usr/bin/msgmerge
> ...
> checking whether NLS is requested... yes
> checking for GNU gettext in libc... yes
> checking whether to use NLS... yes
> checking where the gettext function comes from... libc
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> ...
> seem to be all the relevant bits I can find.
>
>
>
> ???
>
>
> Cheers!
> - Steve
>
> on 03/02/07 00:55 Oden Eriksson said the following:
>> fredag 02 februari 2007 12:03 skrev Steve McInerney:
>>> Evening All,
>>>
>>> have just pushed 3.7.3 out. This remove most of the country name
>>> translations as discussed previously.
>> Hello Steve.
>>
>> It seems like the UTF-8 stuff don't want to work. I have generated this output
>> http://nux.se/stats/se/usage_200702.html like so:
>>
>> LANG=sv_SE LANGUAGE=sv_SE:sv \
>> awffull \
>> --output=/home/sites/nux.se/html/stats/se \
>> --timing \
>> -n nux.se \
>> -t 'Statistics for nux.se' \
>> --use_geoip \
>> /home/logs/nux.se/access_log
>>
>> And:
>>
>> LANG=sv_SE.UTF-8 LANGUAGE=sv_SE.UTF-8:sv \
>> awffull \
>> --output=/home/sites/nux.se/html/stats/se \
>> --timing \
>> -n nux.se \
>> -t 'Statistics for nux.se' \
>> --use_geoip \
>> /home/logs/nux.se/access_log
>>
>>
>> And the formatting in the html is ISO-8859-1 not UTF-8
>>
>>
>> I remember doing like this for the german translation but then the html
>> formatting was oumlouted.
>>
>>
>
> _______________________________________________
> AWFFull mailing list
> AWFFull at stedee.id.au
> http://stedee.id.au/mailman/listinfo/awffull_stedee.id.au
>
>
More information about the AWFFull
mailing list