Problems importing ANSI-encoded contact files

  • Resolved Henk Barreveld

    (@henk-barreveld)


    4 years, 6 months ago

    Hello,

    I am sorry, but I found another problem with the import of contact files; this time in case the contact first name or last name contain diacritics:

    • If the file encoding is UTF-8, the import is correct
    • If the file encoding is ANSI, the import is not correct; the first name or last name that contains diacritics is ignored and not imported

    On my Google Drive you will find a folder, containing two contact files with contact names containing diacritics, UTF-8 resp. ANSI encoded and two screendump files of the Audience page after import of these files. From the file names it will be clear what is what.

    Because Excel, for example, saves CSV-files by default in the ANSI format, you should somehow be able to handle this.

    You will understand that this is related to the UTF-8 BOM problem that I reported two weeks ago.

    Thank you for all your help!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi @henk-barreveld,

    Currently, Email Subscribers supports only UTF-8 encoding which is the standard character encoding for the web.

    You can convert your ANSI encoded CSV file into UTF-8 with the help of online tools like Google Sheets. You can simply open the CSV file in it and then download the CSV. It will save the CSV file in the UTF-8 encoding while downloading.

    Hope this helps you. Let us know if you have any further queries.

    Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi @henk-barreveld,

    Did you get the chance to review our last response? Was it helpful in resolving the issue?

    Let us know if you are still facing the issue or have any queries.

    I am marking this ticket as resolved for now. You can reopen it if the issue still persists.

    Thread Starter Henk Barreveld

    (@henk-barreveld)

    Hello @kishanranawat,

    I just noticed your first reply (now 15 days ago). Somehow I missed it. Sorry!

    Even if everybody would be using UTF-8 encoding for web applications (which is not really the case, unfortunately), that does not apply to other software. As I wrote, if you save an Excel worksheet as a csv-file, the default encoding is ANSI.

    In my view, importing contacts is a serious business. As it is now, it may very well go wrong, causing a mess in your audience lists. Even worse: the user is not aware that it went wrong!

    When your plugin imports an ANSI-file with diacritics, it reports “Total nn contacts have been imported successfully!”, which is incorrect. The contacts have been imported but all name parts with diacritics have been removed. In my view, if the plugin cannot import a file correctly, it should either not import it at all, or provide detailed information what has gone wrong on import.

    The fact that the import file must be UTF-8 encoded should also be in your documentation, but I cannot find it.

    So, even if you consider it to be a hassle to implement other character encodings, which I can imagine, somehow you should handle this.

    Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi Henk,

    Thanks for letting us know the cases when contacting importing may not work as expected due to different encodings.

    We have fixed this issue and currently testing the fix.

    We are planning to release the fix in the next version of the Email Subscribers and will let you know when it gets released.

    Hope this helps you. Let us know if you have any further queries.

    Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi Henk,

    Thanks for your patience and coordination.

    We are glad to inform you that we have released a new version(4.5.6) of Email Subscribers with the fix for the above issue.

    Please update to the latest version and let us know how it goes for you.

    Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi Henk,

    Have you got the chance to review our last reply? Is the issue resolved after updating to the latest version?

    Please let us know. Also, do let us know if you have any further queries.

    Plugin Contributor kishanranawat

    (@kishanranawat)

    Hi Henk,

    I am marking this ticket as resolved with the assumption that the issue has been fixed after updating the plugin to 4.5.6 or above.

    You can reopen the ticket in case if you are still facing the issue.

    Let us know if you have any further queries related to the issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Problems importing ANSI-encoded contact files’ is closed to new replies.