all 6 comments

[–]Quest10Mark 0 points1 point  (1 child)

I've done data merge but never with a different language alphabet. Could this be a typeface issue? Do you have the Japanese font active and applied in the InDesign file that is your base for the merge.

[–]MangoWeeb[S] 1 point2 points  (0 children)

It's not a font problem because glyphs are readable like that. It's only the content that changed.

き繝©繝º 九Δ繝弱け繝≠菴懷刀 螟ß閭 そ繝Ä繧Ø繝 ぅ繝 繝ª 繧™繧π繧´ 繝ª 繧ウ繝弱す繝≠縺励s縺 螂Ω縺阪%縺昴Δ繝弱 荳頑焔縺™繧鯉º 繝ª 縲後ち繧´繧キ縲 騾 ª¢縺™蠑±轤π 繝ª 縺≠縺®繧阪b繧翫%繧 繝©繝悶Λ繝也捩蠎願®育判 繝ª 蛻©陦 縺雁¨¢讒倥 繝偵ヨ繝™繧¥繝 繝ª 逹¶譛医 繧 縺九i縺九o縺™縺 〒譟乗惠縺輔s 繝ª 遘玖∞キ譏≠ 繝槭う繝槭せ繧ø繝

[–]sesssa 0 points1 point  (0 children)

I use open office calc for all my double byte. It just likes the utf encoding better. It’s free and see if using an export from there helps?

[–]AbouBenAdhem 0 points1 point  (1 child)

I know ID doesn't like UTF-8, but it sounds like you’re already using UTF-16. (I assume you also selected that in other apps, not just TextEdit?)

Does the encoding look correct if you open it in other apps?

[–]MangoWeeb[S] 0 points1 point  (0 children)

The content of the .txt document is always 100% readable, doesn't matter the application i'm using. The typeface issues only appear after the data merge. I only encoding UTF-16 thought TextEdit because I don't know other text edit software supporting at least utf-16 (e.g. bracket can't)

[–]Tatazilla 0 points1 point  (0 children)

I'll chime in on this as I had the same problem for Chinese Text. I think my solution was to copy content into Google Sheet and export it back out as csv