Older blog entries for mathrick (starting at number 25)

Ooops, screwup. Will fix in next version of advogato.php. Move along, nothing to see here.

So, I found that dreaded bug I was chasing for several days. It was, uh, in endianness-conversion macros I ripped out of glib, and apparently did that wrong. I feel so stupid now it’s not even funny… :\

PS. Word of advice for you, lads: recalling “best of Sluggy.com” when razor-shaving is, umm, not the best idea one can get. Really ;)

Argued over why C++ sucks, and particularly why multiple inheritance is broken idea and why you should use interfaces instead for 3h straight. Never again, I’m gonna write that advo article one day and then just keep pointing people, and then life will be beautiful again.

mjw: excellent, we have just the sort of thing you need :). Using this plugin export to Advogato is trivial - just edit the source a bit supplying advogato cookie and optionally categories you want to export, drop into your WP plugins dir, activate and voilà - it works.

Update: grrreat, raph dammit, fix UTF-8 support, will ya?

I did new version of wingo’s WP-advogato crossposter plugin. Now it includes support for categories (ie., you can export only posts that are in certain categories, as well as specifically exclude some categories from being posted, even if post would otherwise match exported ones. You can also fallback to old behavior and simply export everything).

Disclaimer: While I tried to test it as much as possible, I take no responsibility for it being bug-free or for that matter, working at all. If that post shows up on advogato, it’s at least a sign that something works :)

TODO:
- include comments link in exported posts
- convert WP’s title into text inlined in posts as published on advogato

steinn, neologisms are issue for almost every language that doesn’t have well-established wordbase in given area, which in case of computing means almost every language != english (and in fact english too, although english is very liberal when it comes to coining new words or stuffing old ones into new role, that helps a lot) at one stage or another. Polish also has that problem, although now there’s enough of material and somewhat more seasoned translations / terms coined that you usually know where to begin. Real fun was back in late ’80s and especially ’90s, where almost every term had 2 or more alternative versions. Now only once in a while you run into certain companies which have that great idea to base PL translation team in Ireland, which feels (ie, you got formally correct translation, but it uses for example infamous “karnacje” for “skins", where rest of .pl has long agreed for “skóry").
Oh, and from time to time we get to see referenda for polish term for “email", which usually produces lots of input and none of change in established terminology, that is “email” ;)

Update: So Advogato uses ISO-8859-1 encoding… Kewl. Everyone, poke raph into switching to proper UTF-8!
Update 2: Err, I kinda failed to make my original point… So here it is: while it is inevitable for language to swallow foreign words for computing, and even many of non-english projects and communities use english internally to avoid ambiguity, and of course ugly-ass translation is far worse and more painful than lack of translaiton, yet I like when language has its own identity and at least partially gets to have its own unique wordbase, even in such an international area as computing. You know, english is fine laguage, and very convenient, but there are other interesting languages out there too :). So bear with initial pains, and in exchange you’ll get icelandic that still feels like icelandic :)