Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Eventual forum upgrade plan
My test install of the forum database shows some of the international categories with glitches where special characters are supposed to be – I guess that was because FluxBB 1.2 did not use UTF-8 and now 1.5 does?
Either way, maybe we need to think about each of these international forums and decide their true value. Considering the fairly small userbase should we be fragmenting even further by making forums for all these languages? Note that the documentation site is lacking in translations anyway, as are a lot of the pophelp entries.
Maybe just concentrate on the most common languages and retire the others. I don’t want to upset anyone by dumping their language but maybe English, French, Spanish, German, Italian plus a few others that get voted.
For example:
- Arabic last post Feb 2012, only 5 topics in total since 2006
- Bulgarian, no topics
- Catalan, 1 topic in 2008
- Etc.
Offline
Re: Eventual forum upgrade plan
philwareham wrote:
My test install of the forum database shows some of the international categories with glitches where special characters are supposed to be – I guess that was because FluxBB 1.2 did not use UTF-8 and now 1.5 does?
I’m getting the same, and I was about to ask you if you were too. The error seemingly is because of the conversion script, but we use already UTF-8 converted database. Have to check which options make it work properly.
There also seems to be an error in the current database — someone has forgotten to update single column; search_words.word is Latin1 while rest of the database is UTF-8. This collation difference makes any join statements to fail (forum updating will fail too). Before updating you will have to first run:
ALTER TABLE `search_words` CHANGE `word` `word` VARCHAR( 20 ) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT ''This should be done to the current forum database (live server) ASAP; that latin 1 is an error. That search index can not possibly be functional.
Last edited by Gocom (2013-10-08 12:26:49)
Offline
Re: Eventual forum upgrade plan
OK, I can do that from home later, as I have remote database access from there.
Offline
Offline
Re: Eventual forum upgrade plan
Will do. I’ll let you know when it’s done.
Offline
Re: Eventual forum upgrade plan
I think that query ran as intended. search_words table word field now shows as encoding UTF-8 Unicode and collation as utf8_bin.
Offline
Offline
Re: Eventual forum upgrade plan
The new forum now supports syntax highlighting. Since all code blocks here aren’t code, highlighting is opt-in. To enable highlighting, start the code block with the name of the language:
bc. html
<strong>Hello world!</strong>If the first line matches a valid language name, the code block is highlighted accordingly. Highlighting is done by Prettify, and syntax coloring looks similar to GitHub.
Supported language identifiers include: apollo, bash, c, coffee, cs, clj, css, dart, go, hs, html, java, js, json, lisp, lua, ml, n, perl, php, proto, python, ruby, rust, scala, sh, sql, tex, vb, vhdl, wiki, xml, xsl, xq and yaml.
Last edited by Gocom (2013-10-09 19:09:54)
Offline
Re: Eventual forum upgrade plan
Gocom wrote:
Supported language identifiers include: apollo, bash, c, coffee, cs, clj, css, dart, go, hs, html, java, js, json, lisp, lua, ml, n, perl, php, proto, python, ruby, rust, scala, sh, sql, tex, vb, vhdl, wiki, xml, xsl, xq and yaml.
but… but… it lacks TXP language highlighting!
Offline
Offline
Re: Eventual forum upgrade plan
I’ve added txp to the list of accepted language identifiers. Incase we ever add its own language definition for it; currently its just an alias for HTML.
Offline
#57 2013-10-10 16:45:55
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,316
Re: Eventual forum upgrade plan
Gocom wrote:
The new forum now supports syntax highlighting.
That’s cool!
syntax coloring looks similar to GitHub.
I’ve had a look at the history of main.js, peeped here and there and was overwhelmed by all the additions you put in there and by the considerations and amendments you’re making. You mentioned only a fraction here. I think Santa will be good to you guys! :)
The forum doesn’t allow me, so you’ll have to imagine the following in #ddd: [phi #2 in main.js ought to be “psi”.]
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Offline
Re: Eventual forum upgrade plan
In the new forums content can be embedded from various services by simply linking to it. It uses the familiar Textile link syntax; a link to a supported service becomes an embedded object if it is in its own paragraph. Links within blobs of text will stay as normal text links to avoid disturbing reading and text flow, and so that you don’t have unrelated embedded item blob attached to end of the post (those aren’t very nice).
Supported services at the moment include Gist, YouTube, Vimeo and Twitter, each when linked, spawning their familiar embed widgets.
Gists:
"$":https://gist.github.com/gocom/5431041Tweet:
"$":https://twitter.com/textpattern/status/386111138699935744YouTube:
"$":http://www.youtube.com/watch?v=BKQ6nINAeq8Vimeo:
"$":http://vimeo.com/42531948To users who don’t have JavaScript enabled, these will display as normal text links.
Last edited by Gocom (2013-10-15 17:30:49)
Offline
#60 2013-10-10 20:02:26
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Eventual forum upgrade plan
Yay, I’ll be a dragon \o/
Justice at last.
But seriously, great work!
Last edited by els (2013-10-10 20:10:24)
Offline