Data merge outputs wrong data

[StefanT]

For example:

data in the csv: ÌGBÇ!Â!%FÎ
data output inaffinity publisher2.5.5: МGBЗ!В!%FО

the scv has been tested in other software and works perfect

[Hangman]

Hi @StefanT and welcome to the forums,

Could you upload your CSV file so we can take a look?

[Old Bruce]

My first guess is the font which is used in Publisher doesn't have the glyphs.

[StefanT]

here is the CSV

 

[StefanT]

@ Old Bruce i don' think it's a font problem, if i paste the item manualy in a text field it is good

[Hangman]

Hi @StefanT,

If you save your data as a CSV UTF-8 (Comma delimited) file rather than a CSV (Comma delimited) file you should be good to go. Alternatively, save it as a .xlsx file...

Note: because you've used a semi-colon as your separator some of the data doesn't format correctly because certain cells include a semi-colon as part of the data set so separate incorrectly...

[StefanT]

Hi Hangman,

the UTF export works, but that means a separated export is needed depending the software the receiving user is using, the UTF version does not 
work in indesign for instance, and the export that works in indesign is useless in affinity publisher, apparently they don't use industry standards

Thank you for finding this out

[Hangman]

Hi @StefanT,

An .xlsx version should work across all software, assuming of course InDesign and any other software making use of the Data file can accept .xlsx files...

[StefanT]

Hi @Hangman, 

Indesign only accepts .csv and .txt unfortunately

[Hangman]

Hi @StefanT,

From reading numerous posts in the Adobe forums the issue seems to be with InDesign failing to read UTF-8 files properly... The suggestion by several users is to try UTF-16BE or UTF-16LE but neither format is supported by Publisher...

Out of interest, do either of the attached work in InDesign?

[StefanT]

Hi @Hangman, 

It was indesign only in the past, 2 licenses, one for the person who did graphic work for print & web
and 1 that was reserved and was used by anyone who needed it, that changed recently with the arrival of a
second designer, new adobe licenses were out of the question, luckily most of our people have canva,
and recently we had access to affinity through canva, which looks like a good alternative 

[Hangman]

Hi @StefanT,

So it sounds as though you are effectively transitioning away from Adobe to Affinity Software from Canva/Serif...

For your Data Merge requirements does this mean you'll be able to adopt the UTF-8 encoded CSV file or .xlsx files moving forward?

[StefanT]

Hi @Hangman, 

Yes, it's a little change in workflow but that shouldn't be a problem

[Hangman]

Hi @StefanT,

That's good to hear and I'm glad you have a workable solution...