{"push_id":606969016,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"61a3ace9f42a37640b1ec18fad776ba7c1f61714","before":"98c532b38589945717ff17ed344a358479074e5b","commits":[{"sha":"61a3ace9f42a37640b1ec18fad776ba7c1f61714","author":{"email":"8a36cd9f353d245c534f8bb105741cdef632bfd5@yahoo.fr","name":"Julien Nabet"},"message":"Related tdf#50133: Wrong underlining in Reports\n\nBy running some tests, I noticed double wave didn't appear when opening report in non edit mode.\nFirst you must know that to indicate \"double wave\", xml contains these 2 information:\nstyle:text-underline-style=\"wave\" style:text-underline-type=\"double\"\n\nThe problem is the reading order of the parser doesn't seem the same each time.\nSo if it reads style then type, it's ok thanks to this part:\n    132             case awt::FontUnderline::DOUBLE:\n    133                 // A double line style has priority over a bold line style,\n    134                 // but not over the line style itself.\n    135                 switch( eUnderline )\n    136                 {\n    137                 case awt::FontUnderline::SINGLE:\n    138                 case awt::FontUnderline::BOLD:\n    139                     break;\n    140                 case awt::FontUnderline::WAVE:\n    141                 case awt::FontUnderline::BOLDWAVE:\n    142                     eNewUnderline = awt::FontUnderline::DOUBLEWAVE;\n    143                     break;\n\nbut if the parser read type in the first place then style, the case FontUnderline \"DOUBLEWAVE\" wasn't managed\n\nChange-Id: Ie090507898e537827eebaae157dfac248baa43f1\nReviewed-on: https://gerrit.libreoffice.org/14801\nReviewed-by: Caolán McNamara <caolanm@redhat.com>\nTested-by: Caolán McNamara <caolanm@redhat.com>","distinct":true,"url":"https://api.github.com/repos/LibreOffice/core/commits/61a3ace9f42a37640b1ec18fad776ba7c1f61714"}]}