[en] Bootstrap — accordion closes modal

Becau­se Boot­strap events are not name­spa­ced until they rele­ase ver­sion 3.0 (see https://​github​.com/​t​w​i​t​t​e​r​/​b​o​o​t​s​t​r​a​p​/​i​s​s​u​e​s​/​3​736), they con­flict with each other. It cau­ses for instan­ce clo­sing modals when swit­ching accor­dion tabs — they both listen to „hid­den” event. A sim­ple, glo­bal solu­tion is not to use data-toggle=„collapse” but fol­lo­wing code (that atta­ches „live”, 1.9.x jQu­ery style):

$(document).on('click', 'a.accordion-toggle', function(event) {
    event.preventDefault();
    var parent = $(this).parent().parent(),
        body = parent.find('.accordion-body');
        
    // hide currently shown group
    parent.parent().find('.accordion-body.collapse.in').collapse('toggle').on('hidden', function(event) {
        event.stopPropagation();
    }); 
    
    // show newly clicked group
    body.collapse('toggle').on('hidden', function(event) {
        event.stopPropagation();
    });
});

Roundcube ATT####.dat in Outlook with diacritical characters

When you get reports that some people get e‑mails from Round­cu­be that have ATT####.dat attach­ments, check if they­’re using Micro­soft pro­grams, espe­cial­ly Outlo­ok Express. They don’t (of cour­se) imple­ment the most recent RFCs, so if attach­ment name con­ta­ins dia­cri­ti­cal cha­rac­ters (such as Polish ą, ć, ś, etc.) it gets cor­rup­ted. When using Round­cu­be, the solu­tion is quite sim­ple — search the main con­fig file for „mime_param_folding” and chan­ge its value from 0 to 1.

[en] Solution to Postgres JDBC driver ignoring charSet directive with SQL_ASCII database

New” Post­gres JDBC dri­vers check data­ba­se engi­ne ver­sion and if it’s not below 7.3 they will igno­re char­Set dec­la­ra­tion. It bre­aks enco­ding of 8‑bit cha­rac­ters if data­ba­se has SQL_ASCII enco­ding (which basi­cal­ly means DONT_CARE_ANYTHING_GOES). If your data­ba­se is set to SQL_ASCII and in reali­ty it sto­res e.g. Win­dows-1250 (CP1250) cha­rac­ters, JDBC dri­ver will assu­me incor­rect enco­ding and dia­cri­ti­cal cha­rac­ters will be broken.

Even tho­ugh I under­stand the reasons given by Post­gres deve­lo­pers for this (SQL_ASCII is NOT sup­po­sed to be used with any­thing other than 7‑bit cha­rac­ters and it is obso­le­te), the solu­tion they­’re sug­ge­sting (to dump the db, and convert it to UTF‑8) is not always possi­ble. For instan­ce, I would have a hard time tel­ling my custo­mer to do it, espe­cial­ly becau­se the­ir old softwa­re might break.

So I’ve pat­ched the JDBC dri­ver to accept char­Set direc­ti­ve in JDBC URLs and also added a method set­Char­set to PGSimpleDataSource.

Here you can down­lo­ad it: Post­gres JDBC dri­ver — char­Set patched