Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
The language that Instiki is written in, ruby, got an upgrade recently (to 1.9) and Instiki is now compatible with the updated version. The nLab has just switched today to 1.9. As with any such upgrade, it may have introduced odd behaviour, but it does seem to be working okay. Please record any changes you may notice - both positive and negative! This change also affected itex in that it needed recompiling.
On that, it's possible that pages generated during the switch-over didn't get itex'ed correctly. Due to the cache, these pages may persist. So if a page displays without the mathematics rendered correctly, log it here and we'll force it to be regenerated (if you can't wait that long, do a trivial edit on it - that forces regeneration).
(If you want to email Jacques directly with bugs then please also record them here so that the rest of us know what they were, and some things that might seem like instiki issues actually aren't so need to be brought to the attention of the lab elves.)
Hi Andrew,
I just noticed a problem with a page on my personal web: unless I am mixed up the page
path structured smooth (oo,1)-toposes
used to display correctly. Now the itex in the standout box in the section "bare" doesn't disyplay correctly. Could that be due to the update?
Because, what is worse, here is the real problem: the software won't let me edit the page! When I hit edit I get a page saying "Internal Application Error".
I would appreciate if you could just let me know if you can easily figure out what's going on. Otherwise I'll contact Jacques.
(Also, the new boxes around all cross-web links mess up the look of all my personal web pages, that all have plenty of links to the Lab. Can I get rid of these boxes?)
Looking in to it.
Aaagh. This is due to a character encoding issue - the database stores everything in one character set but instiki uses a different one. The problem is that 'infinity' symbol in the page name. I've sent an email to Jacques about it, but I'm going to drop back down to ruby 1.8 for the moment due to the timing.
That also seems to have fixed that section of mathematics as well, which suggests it was another ruby1.9 issue. I'll have to see if I can figure out why that wasn't working.
Thanks, Andrew, for your efforts!!
Progress report: the issue with page names has been fixed, or at least it ought to have been. I've been able to edit pages with non-standard unicode characters in their names. There may still be issues buried in there, so just let me know if anyone spots anything.
The mathematics issue is, I think, related to the same issue. The problem seems to be due to an infinity symbol (∞) in text embedded in mathematics. For the moment, I've switched it to the word "infinity", sadly putting the entity (∞) doesn't work as it gets converted to ∞ at some point (this shouldn't happen, btw). itex doesn't like unicode symbols for some reason so complains.
Actually, this conversion of entities to unicode is something we've seen this before and it caused quite a lot of smoke so I'm reverting to 1.8.6 again.
Incidentally, Urs, do you want your standout boxes constrained in height in the same way that query boxes are? That is, if they get long then they get little scroll bars. While that's appropriate for query boxes, I'm not so sure for standouts. I think I fixed this on the main nLab, but I notice that it's not fixed on your personal web. Shall I fix that for you?
Oh, if you can, please fix it on my web, too. I would like standout boxes never to produce a scrollbar, yes.
Done.
Thanks a million, Andrew.
Hmm, not sure what's going on with the standout boxes. It seems to be only the one on that page that gets a scrollbar.
Zoran reported that 'recently revised' doesn't work. That seems to be fixed now, but 'all pages' is now bust.
(For those wondering at what's going on, it's all to do with character sets. The database stores stuff using Latin1, Instiki internally uses utf-8. With Ruby1.8 this didn't seem to be a problem. Ruby1.9 seems to be less forgiving so Jacques has to put in explicit "convert to utf-8" statements all over the shop. Apparently, converting the database to utf-8 wouldn't be a good idea as MySQL's implementation is bust (though that's hearsay - if anyone knows better, let me know).)
Okay, recently_revised and all_pages now work. It's possible that that's the lot, keep an eye out for other "application error"s.
Yay!Thanks
1 to 15 of 15