View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021798 | mantisbt | printing | public | 2016-10-12 08:44 | 2019-01-11 06:29 |
Reporter | mboutell | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.3.1 | ||||
Target Version | 1.3.6 | Fixed in Version | 1.3.6 | ||
Summary | 0021798: Print reports failed : special characters are not formatted | ||||
Description | When printing reports in word format, special characters like "é" or "à" are replaced by symbols. Is there any solution ? This issue appears after migrating from 1.2.17 to 1.3.1 | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Could you please clarify the problem, providing steps to reproduce and screenshots to illustrate the issues you're facing ? |
|
Please find in attachment an example (The resolution should be empty, and the fields contains symbols) Steps to reproduce : |
|
Thanks for the feedback.
'5' is not a standard resolution code [1], can you please ensure you've followed the guidelines for customizing enumerations [2] and provide the relevant configuration settings if the problem persists. [1] https://github.com/mantisbt/mantisbt/blob/release-1.3.1/config_defaults_inc.php#L3343 Regarding accented characters, it looks like an ANSI<=>UTF-8 encoding issue. Not sure whether this is caused by MantisBT code or local setup. I don't have time to look into it right now. |
|
I assume mboutell forgot to copy his custom_* files from his old 1.2.17 version to the config folder of the new 1.3.1 installation.
|
|
@atrol : sorry but the custom_* files are in the "config" folder... I didn't set any enumeration for resolution field... |
|
I am quite sure you did. Do you set $g_resolution_enum_string in config_inc.php? |
|
$g_resolution_enum_string = '10:open,20:fixed,30:reopened,40:unable to duplicate,50:not fixable,60:duplicate,70:not a bug,80:suspended,90:wont fix'; It's the only existing line in my files. |
|
Check database table mantis_bug_table for entries where resolution is 5 Did you set $g_default_bug_resolution ? |
|
mboutell, You did not provide feedback; I am therefore resolving this issue as "no change required". Feel free to reopen the issue at a later time and provide the requested information. |
|
My corrupted file is in attachment, I still have the encoding problem. |
|
Run admin/check/index.php If so, this is what dregad wrote 0021798:0054219
|
|
No there is no warnings for UTF-8 |
|
The attached .DOCX file is not generated by MantisBT as we generate .DOC files. There is no problem when using Libre Office, but I am able to reproduce the issue using Microsoft Word 2013 One difference between 1.2.x and 1.3.x is that we longer have the following line in header of the file <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
|
So, what should I do ? |
|
Is there any workaround ?Did you have time to have a look on this issue ? |
|
a) Open in Libre Office, store in MS Office Format
No, you shouldn't expect that I will fix it. |
|
@mboutell maybe a workaround that works for you, have a look at 0022103 |
|
@atrol thanks I'm gonna try this ! |
|
@atrol it's perfect it's working thank you ! |
|
MantisBT: master-1.3.x a172cd07 2017-01-31 10:30 Details Diff |
Add UTF-8 header to Office Word output Fixes 0021798 |
Affected Issues 0021798 |
|
mod - print_all_bug_page_word.php | Diff File | ||
MantisBT: master-2.2 17d6796a 2017-01-31 10:30 Committer: dregad Details Diff |
Add UTF-8 header to Office Word output Fixes 0021798 Signed-off-by: Damien Regad <dregad@mantisbt.org> Cherry-picked from 1.3.x (23da4e0c814e6ed5ee1fc51be6d2b5f15866b7ca) following incorrect merge conflict resolution in 75ef07835bc3771c9632ed20aa6512ed9d6a17cc. |
Affected Issues 0021798 |
|
mod - print_all_bug_page_word.php | Diff File |