[01:00] <emunkki> vbabiy, http://emonk.fi/work/ubuntu/feature_tour_filmstrip_mockup_2.png
[01:01] <emunkki> vbabiy, we decided to put up something like that
[01:01] <emunkki> we'll talk more later
[01:01] <emunkki> will watch a movie and then sleep
[01:01] <vbabiy> emunkki: I do like it so far
[01:01] <vbabiy> Sorry I had to leave
[01:01] <emunkki> yeah np :)
[01:01] <vbabiy> Yeah, maybe we can talk tom
[01:02] <emunkki> sure
[01:02] <emunkki> i'll be back in maybe 12 hours
[15:54] <qense> What the heck is going on with the wiki? It's terribly slow.
[15:54] <qense> I'm getting 111 errors and POST mistakes
[16:01] <newz2000> qense: can you paste an error or a screenshot of it?
[16:01] <nand> qense: there was a new version put online
[16:01] <newz2000> oh really?
[16:01] <nand> didn't know?
[16:01] <qense> ah, that was probably causing it :)
[16:01] <nand> supposed to be faster, and with some additional features :)
[16:01] <newz2000> nand: no, I finished the theme for the 1.6 upgrade weeks ago
[16:01] <newz2000> yes, openid support, plus better spam prevention
[16:02] <newz2000> unfortunately, major new wiki syntax
[16:02] <qense> That's why my new page looks malformed!
[16:03]  * nand hopes he won't have to rewrite a bunch of them
[16:03] <newz2000> the migration process was supposed to deal with that, but if you put your page in after the migration then it would certainly cause a prob
[16:03] <newz2000> I'm hoping that once the wiki settles from the upgrade creating/editing is faster. It used to be so slow because of the way it checked for subscribed users
[16:03] <newz2000> oh, search should be much faster now too
[16:05] <qense> How do you create a link where the clickable text is different from the name of the page you're linking too?
[16:05] <qense> ["page1|desc"] doesn't work anymore
[16:05] <newz2000> is there a help below the edit box?
[16:05]  * newz2000 looks too
[16:06] <newz2000> oh, right [[  ]]
[16:06] <newz2000> [[link|text\\
[16:06] <newz2000> \\ == ]]
[16:06] <qense> that's solving it
[19:34] <nand> hey, a small website question: what is the preferred way to handle i18n in a website? Hardcoded? Gettext via some lib?
[19:35] <nand> and what's the best way to store it concerning performance? DB, included file?
[19:35] <emunkki> depends on the website
[19:35] <emunkki> and what you want to achieve
[19:36] <emunkki> and how often the translations are going to change
[19:36] <nand> well, the website is brainstorm: there is not so much strings there
[19:37] <nand> anyone knows how reliable is php-gettext? (not updated since 2006)?
[19:38] <emunkki> don't know
[19:38] <emunkki> how high traffic?
[19:38] <emunkki> basically if you're using db anyway, i'd suggest creating a table
[19:39] <emunkki> and it's the best for updates
[19:40] <nand> the advantages with text files (.po) is that some tools exists to edit them easily
[19:47] <emunkki> nand, i'd prefer db.
[19:47] <emunkki> nand, especially if you're using db anyway