SiComponents Forums

I've found a fix for this , the way i've come across it is to write directly to charset.sil ( save the charset ) then add the ones that are missing ( then click load ) it works a treat , once saved its easy to spot that there are missing items in the file , i add them and its fixed. be nice if you c...

i've just noticed that on some reports the charset area is blank with no entries , do you have any way to get it back ? or rescan the report and pick up the labels / components that need to change charsets dependent on language ie korean , Japanese and english. ( also for forms , as i noticed some f...

Yes the its included in the first two bytes of the XML file ... not on each string



Delphian


we tested it at the office and it now imports properly

I've found the reason why the question marks appear , it seems our importing program was placing the unicode header of $FFFE on each unicode word in the XML import. We have removed it and it now works perfectly. maybe on your XML import you should scan the text and if the first wide char = $FEFF the...

Yes it gives the same error when i use find translation. it only happens with japanese text , we have korean as well and its perfect.


Kind Regards



Dephian

When i try to use Suggest Translation or Auto Translate i get a Question mark appear in front of my unicode japanese text ie i am trying to translate the word / phrase " Booking Date " , which i have 予約作成日 in the dictionary and it returns ?約作成日 i believe the point where the problem occurs...