You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A support client noticed that the CSV response file (when opened in Notepad) shows LF characters (carriage return / line break) in the CSV file. This pattern happens for the form questions/labels, but not for the default columns such as submission ID, submission date, receipt codes.
Expected behaviour
This inconsistency could be mitigated by either:
displaying column headings in the language of submission
choosing to use slashes across columns to separate EN and FR
choosing to use line breaks across columns to separate EN and FR
showing an ID instead of a string
In terms of readability, one language might be easier to follow, but risks losing the association between EN and FR if data is processed unilingually.
In terms of scannability, a line break makes it easier to see the question label at a glance in the language of choice. Though there is still additional noise with both languages.
In terms of other possibilities, there's also the machine-readable tags work that might factor into this if an ID can be used instead of collating EN and FR strings.
Description
A support client noticed that the CSV response file (when opened in Notepad) shows LF characters (carriage return / line break) in the CSV file. This pattern happens for the form questions/labels, but not for the default columns such as submission ID, submission date, receipt codes.
Expected behaviour
This inconsistency could be mitigated by either:
In terms of readability, one language might be easier to follow, but risks losing the association between EN and FR if data is processed unilingually.
In terms of scannability, a line break makes it easier to see the question label at a glance in the language of choice. Though there is still additional noise with both languages.
In terms of other possibilities, there's also the machine-readable tags work that might factor into this if an ID can be used instead of collating EN and FR strings.
Steps to reproduce
Details
Screenshots or videos
Additional context
https://gcdigital.slack.com/archives/C03T4FAE9FV/p1734034022225009
https://dev.to/pranjal-barnwal/understanding-line-break-types-cr-lf-lf-and-cr-3lg2
The text was updated successfully, but these errors were encountered: