Search options

Indeed this sounds weird. Perhaps this is to enable people with only static html hosting to start a blog using their existing host? Otherwise I really wonder why go through Blogger.com if you could set up your own system on your own server.

From another perspective, seeing it's now a part of the Google "machine", perhaps this means that as Blogger.com processes each post, Google.com immediately gets the page indexed? Since all the page content (and links) are maintained by Blogger.com, this also goes to elliminate dead links? As weblogs contain more and more information, seizing this opportunity to have first-hand access to weblog posts perhaps has some commercial value?

But then I'm not an IT person, these are just me wondering aloud.

As for me...I'm reading up slowly on the possibility of integrating WordPress and PunBB. I think the two make a perfect pair, although I am really at a loss when it comes to a rationale for running the two together at the same time, given that it's going to be a personal weblog.

It does seem that jacobswell misunderstood Paul here. Paul was agreeing to the problem and merely suggesting a solution to Rickard, the example was made up randomly just for the sake of illustrating a possible difference.

With the Chinese language pack, I've came up against word order problems, too. I was able to adapt most of it, since Chinese really has a very loose structure. But I do agree that localization should not be based on words but on full sentences or even paragraphs/messages as a whole.

When basing translations on words, word order is not the only problem. Sometimes a more serious problem is word meaning. A word XYZ that has meaning A and B in English, and hence has it's translation string shared in two places, may be completely un-acceptable in another language, where the meanings A and B simply has to use different words PQR and STU. Lastly, a problem that doesn't come up all the time in technical translation, is when there are non-translatable words or phrases (this is more likely to occur when there is a lot of cultural content).

Fortunately, PunBB (and software localization in general) does not use a lot of complex and compound sentences. Most of the problems described above can be solved with a little creativity on the part of the translator, or experience and study, which may not always be available when it comes to voluntary localization of free software.

PS: I work as a translator between Chinese and English.

Thanks very much! It's working nicely now. I think I'll start testing style problems in Mozilla as well.

Hmmm....USD$25 is approximately NTD$800 or so here...not a bad deal. So count me in, it's time for me to drop my A4 scrap paper.

Oh, I use a optical mouse, hopefully it doesn't matter?

OK, thanks. I've grabbed it off PunBB.org and eliminated all traces of the old version . Will use it as base for any modifications.

I must say I'm really impressed by how easy it is to localize PunBB, at least for the user. Really good work!

I'd love to see this implemented, since I've still got the habit of _italics_ and *bold* from DOS days.

But I wonder how well these kind of things work with double-byte character sets.