-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commas in text strings act as delimiters and cause the generated CSV file to have content that gets shifted to the next column #8
Comments
The problem is caused by commas in the body of the message. Every time a comma is encountered the next content in line gets populated to the next column. Returns do not as indicated by the \n.
… On Feb 2, 2018, at 8:55 AM, Noone ***@***.***> wrote:
This problem was fixed in a previous version but has resurfaced in th current 2.0 version
<https://user-images.githubusercontent.com/33180619/35739234-97d10e96-07f6-11e8-869f-3a04ce6904d0.png>
<https://user-images.githubusercontent.com/33180619/35739248-a42c26da-07f6-11e8-9211-ac16c808f841.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#8>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfEH01wu-CsL4ckBTzdSZMN_Zaj3B2Uoks5tQyHwgaJpZM4R3TBV>.
|
I receive these errors :
… On Feb 3, 2018, at 8:18 AM, PostCardsAway ***@***.***> wrote:
The problem is caused by commas in the body of the message. Every time a comma is encountered the next content in line gets populated to the next column. Returns do not as indicated by the \n.
> On Feb 2, 2018, at 8:55 AM, Noone ***@***.*** ***@***.***>> wrote:
>
> This problem was fixed in a previous version but has resurfaced in th current 2.0 version
>
> <https://user-images.githubusercontent.com/33180619/35739234-97d10e96-07f6-11e8-869f-3a04ce6904d0.png>
> <https://user-images.githubusercontent.com/33180619/35739248-a42c26da-07f6-11e8-9211-ac16c808f841.png>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub <#8>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfEH01wu-CsL4ckBTzdSZMN_Zaj3B2Uoks5tQyHwgaJpZM4R3TBV>.
>
|
will check now and let you know? Have you tried with my example?. It is working fine for me! Can you please let know the old version, you used so for now. |
THANKS AS ALWAY !
… On Feb 5, 2018, at 12:29 AM, Vignesh ***@***.*** ***@***.***>> wrote:
will check now and let you know?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfpLy2vIeCqEgZUNf0cKx6PUrnVptMpAks5tRp-7gaJpZM4R3TBV>.
|
Do you have this issue? Shall i close this ticket? |
Have you fixed this problem ?
If so have you create a new version ?
… On Feb 7, 2018, at 3:36 AM, Vignesh ***@***.*** ***@***.***>> wrote:
Closed #8 <#8>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfpLywkR8MdmZy1EIx-nlRnLFJHX2f3sks5tSW6CgaJpZM4R3TBV>.
|
Hi @DogandElk , i was unable to reproduce this issue. Can you please provide some sample data? |
Give sample formatted string which you used in the app? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This problem was fixed in a previous version but has resurfaced in th current 2.0 version
The text was updated successfully, but these errors were encountered: