Many Microsoft software rely on UTF-8 signature(BOM) to determine file encoding.
Missing BOM can lead to strange side effects that is hard to understand.

CommentFileSizeAuthor
#5 csv_serialization-2859030-2-5-interdiff.txt1.12 KBrosk0
#5 csv_serialization-2859030-5.patch1.68 KBrosk0
#2 csv_serialization-2859030-2.patch1.67 KBrosk0

Comments

RoSk0 created an issue. See original summary.

rosk0’s picture

rosk0
he/him
Primary language Russian
Location Wellington
commented
Assigned: rosk0 » Unassigned
Status: Active » Needs review
StatusFileSize
new csv_serialization-2859030-2.patch1.67 KB

Patch to introduce optional BOM support in encode operations.

My colleague currently working on patch for Views Data Export module to provide UI for this option.
Will link to the issue when patch will be posted.

undertext’s picture

undertext commented
Status: Needs review » Reviewed & tested by the community

Patch looks good and works for me.
Only one minor thing, maybe variable should be called $useUTF8Bom for more clarity.
Changing status to RTBC to get feedback from module maintainer.

hgoto’s picture

hgoto commented

+1 to RTBC. And I agree with @undertext as for the variable name. Thanks.

rosk0’s picture

rosk0
he/him
Primary language Russian
Location Wellington
commented
StatusFileSize
new csv_serialization-2859030-5.patch1.68 KB
new csv_serialization-2859030-2-5-interdiff.txt1.12 KB

Changed property name as requested.

hgoto’s picture

hgoto commented

@RoSk0 thanks!

  • grasmash committed 12812ec on 8.x-1.x authored by RoSk0 
    Issue #2859030 by RoSk0: Support UTF-8 signature in export

grasmash credited grasmash.

grasmash’s picture

grasmash commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.