I think that we probably have a few issues related to wide strings in the SqueakSource code, and these issues certainly will effect source.squeak.org in the same way that we have seen on squeaksource.com. The only difference being that we do not happen to have any author names with multibyte characters registered on source.squeak.org at the moment.
When I was originally loading the old SqueakSource onto our squeak.org servers, I found some problems with the image updating its repository from disk, and at the time I chose to work around them manually in order to get the system up and running. But there seem to be places where the identity of an author is saved in the repository (in the image, not on disk), and stored with possibly different encoding in the MCZ file names on disk, and may be stored with yet another possibly different encoding internally within the MCZ file.
The good news is that the squeaksource.com files and image give us enough real life data that we should be able to locate the problem cases and think about how to handle them properly. For example, the ss.log file shows evidence of continuing problems related to six specific files:
2013-12-21T18:39:10.089+00:00 RECOVERING FelTimetable/FelTimetable-M·Sa.53.mcz 2013-12-21T18:39:11.353+00:00 RECOVERING FelTimetable/FelTimetable-M·Sa.52.mcz 2013-12-21T18:39:11.602+00:00 RECOVERING FelTimetable/FelTimetable-M·Sa.55.mcz 2013-12-21T18:39:12.884+00:00 RECOVERING FelTimetable/FelTimetable-M·Sa.66.mcz 2013-12-21T18:39:14.193+00:00 RECOVERING FelTimetable/FelTimetable-M·Sa.54.mcz 2013-12-21T18:39:15.45+00:00 RECOVERING FelTimetable/Seaside2.8a1-M·Sa.49.mcz
So some follow up is needed. But maybe not today, for now I'm just happy to have the site running again :-)
Dave
On Sun, Dec 22, 2013 at 05:31:13PM +0100, Levente Uzonyi wrote:
On Sun, 22 Dec 2013, Bob Arning wrote:
David,
Here is an alternative that tries to print the item rather than delete it. You can revert the previous fix, if you like.
The problem with this solution is that it will print a string using UTF-8 encoding, but Seaside will return a XHTML page with ISO-8859-1 endocing. There are two ways to solve it: 1: use NCRs[1] to encode the names. This might be a problem, because one has to make sure that seaside won't encode the & characters. 2: change the default character encoding to UTF-8, which might lead to other problems.
Levente
[1]https://en.wikipedia.org/wiki/Numeric_character_reference
Cheers, Bob
'From Squeak3.11alpha of 6 January 2010 [latest update: #8824] on 22 December 2013 at 10:32:55 am'!
!WideString methodsFor: 'converting' stamp: 'raa 12/22/2013 10:31'! printHtmlOn: aStream
??? self squeakToUtf8 printHtmlOn: aStream! !
On 12/22/13 12:03 AM, David T. Lewis wrote:
Bob,
This is absolutely great, thank you so much for the help. I just loaded your patch into the running image, and the http://squeaksource.com web interface is back to normal again.
Dave
On Sat, Dec 21, 2013 at 11:25:59PM -0500, Bob Arning wrote:
David,
The short answer is that two users (St?ane Munioz St?ane Munioz) have wide characters in their name and this does the damage. The method below is a quick hack to filter these 2 out of the list and all seems good.
Cheers, Bob
'From Squeak3.11alpha of 6 January 2010 [latest update: #8824] on 21 December 2013 at 11:21:03 pm'!
!SSHome methodsFor: 'statistics'! membersNew | t1 | t1 := self statistics membersNew. ^ t1 reject: [:t2 | t2 asString anySatisfy: [:t3 | t3 asciiValue > 255]]! !
On 12/21/13 9:25 PM, David T. Lewis wrote:
On Sat, Dec 21, 2013 at 07:41:08PM -0500, Bob Arning wrote:
If you click one of the links on the first page, the next page looks good. If you then go back, the css from page 2 makes page1 look a little better. So, the breakage is limited. Any way to share the image?
Thanks Bob,
A copy of the image is at http://box2.squeak.org/ss_image_for_bob.zip
The zip is encripted, I will send the password to you in a separate email.
Dave