[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2018-07-28 Thread Ineiev
Update of sr #109423 (project administration): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #7: It turns out

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2018-03-03 Thread Ineiev
On Wed, Dec 13, 2017 at 08:32:11AM -0500, Ineiev wrote: > My idea was: new entries are prefixed with a magic string no old entries > begin with; when extracting, Savane checks if the string begins with > the prefix and decodes it when it does. I've just pushed and installed a workaround. signatu

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2018-03-03 Thread Ineiev
Update of sr #109423 (project administration): Status:Works For Me => In Progress ___ Follow-up Comment #6: The notifications still come broken

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2018-03-03 Thread Ineiev
Update of sr #109423 (project administration): Status:None => Works For Me ___ Reply to this item at: __

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2018-03-03 Thread Ineiev
Follow-up Comment #5, sr #109423 (project administration): I've just pushed and installed a workaround: whenever a new comment is written, it reads back what it actually inserted in the database, and if it differs from the original text, it base64encodes it and inserts with a magic prefix. When e

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-13 Thread Ineiev
On Tue, Dec 12, 2017 at 11:05:30AM -0700, Bob Proulx wrote: > Ineiev wrote: > > Bob Proulx wrote: > > > Can we scan the data before storing it > > > and detect when we will have the problem and then encode it then? > > > > Probably we could. I think some UTF-8 parsing would be needed, it's > > som

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-12 Thread Bob Proulx
Ineiev wrote: > Bob Proulx wrote: > > Can we scan the data before storing it > > and detect when we will have the problem and then encode it then? > > Probably we could. I think some UTF-8 parsing would be needed, it's > somewhat harder than to encode unconditionally. If we encode unconditionally

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-12 Thread Ineiev
On Tue, Dec 12, 2017 at 12:30:42AM -0700, Bob Proulx wrote: > Ineiev wrote: > > The question is what to do. we could wait for MySQL or store new messages > > in something like base64, with a magic prefix. > > Upgrading quickly is problematic. And trying to upgrade just the > database system and n

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-11 Thread Bob Proulx
Ineiev wrote: > The question is what to do. we could wait for MySQL or store new messages > in something like base64, with a magic prefix. Upgrading quickly is problematic. And trying to upgrade just the database system and not the clients is also problematic. Or perhaps the reverse if that is t

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-11 Thread Ineiev
On Fri, Dec 08, 2017 at 01:59:21PM -0700, Bob Proulx wrote: > Ineiev wrote: > > This looks like a MySQL bug : the > > string breaks when inserted. FYI: Savannah runs on top of 'mysql Ver 14.14 > > Distrib 5.5.58, for debian-linux-gnu (x86_64) using readline

Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-08 Thread Bob Proulx
Ineiev wrote: > This looks like a MySQL bug : the > string breaks when inserted. FYI: Savannah runs on top of 'mysql Ver 14.14 > Distrib 5.5.58, for debian-linux-gnu (x86_64) using readline 6.3'. Excellent debugging! Bob

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-12-08 Thread Ineiev
Follow-up Comment #4, sr #109423 (project administration): This looks like a MySQL bug : the string breaks when inserted. FYI: Savannah runs on top of 'mysql Ver 14.14 Distrib 5.5.58, for debian-linux-gnu (x86_64) using readline 6.3'.

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-11-28 Thread Ineiev
Follow-up Comment #3, sr #109423 (project administration): Thanks for the sample; curiously, preview seems to be unaffected. ___ Reply to this item at: __

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-11-28 Thread Ineiev
Follow-up Comment #2, sr #109423 (project administration): Does it reproduce? begin 😀end ___ Reply to this item at: ___ Message sent via/by Savanna

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-11-28 Thread David Corbett
Additional Item Attachment, sr #109423 (project administration): File name: 1f600.txt Size:0 KB ___ Reply to this item at: ___

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-11-28 Thread Ineiev
Update of sr #109423 (project administration): Assigned to:None => ineiev ___ Follow-up Comment #1: Could you attach a sample text in a file? __

[savannah-help-public] [sr #109423] Non-BMP characters truncate comments

2017-11-27 Thread David Corbett
URL: Summary: Non-BMP characters truncate comments Project: Savannah Administration Submitted by: dscorbett Submitted on: Mon 27 Nov 2017 09:09:10 PM UTC Category: Savannah tracker