| View previous topic :: View next topic |
| Author |
Message |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Wed Aug 06, 2008 6:00 pm Post subject: support for non-latin characters |
|
|
| Please tell me if there is a support for non-latin character transformation, particularly from MS Access and MySQL. When I tested MS Access database with Unicode chars to transform to other MS Access database and to MySQL, question marks appear instead of non-latin chars. Thanks |
|
| Back to top |
|
 |
Sergei
Joined: 26 Jul 2007 Posts: 969
|
Posted: Thu Aug 07, 2008 12:26 pm Post subject: Re: support for non-latin characters |
|
|
| mbojanks wrote: | | Please tell me if there is a support for non-latin character transformation, particularly from MS Access and MySQL. When I tested MS Access database with Unicode chars to transform to other MS Access database and to MySQL, question marks appear instead of non-latin chars. Thanks |
Hi mbojanks!
General Information. Apatar does not convert texts from one encoding to another. Apatar uses encoding of client PC java machine.
Could you please elaborate on how did you notice that question marks? Via phpMyAdmin? If so, it might be just wrong displaying of symbols. To check this, you should do just only "Preview results" on the MySQL connector and check if Apatar displays these question marks.
Let me know about your results.
Regards,
Sergei |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Thu Aug 07, 2008 5:34 pm Post subject: Question marks in Preview results |
|
|
| Those question marks appear in the Preview results window, both from target MS Access and MySQL connectors... I tested on my local windows xp machine with JRE 1.6.0_07, both times I tried to transform (without any function in between) Serbian Cyrillic unicode data from one Access table into another (the first test) and then into a MySQL database table (the second test), and both times I obtained question marks in the target table's connector Preview results window... Perhaps batch file should contain encoding switch for proper operation on non-latin chars (to compile into different encoding)... Thanks for your quick response |
|
| Back to top |
|
 |
alex Apatar Team Member

Joined: 30 Mar 2007 Posts: 464
|
Posted: Fri Aug 15, 2008 5:58 pm Post subject: Re: Question marks in Preview results |
|
|
| mbojanks wrote: | | Those question marks appear in the Preview results window, both from target MS Access and MySQL connectors... I tested on my local windows xp machine with JRE 1.6.0_07, both times I tried to transform (without any function in between) Serbian Cyrillic unicode data from one Access table into another (the first test) and then into a MySQL database table (the second test), and both times I obtained question marks in the target table's connector Preview results window... Perhaps batch file should contain encoding switch for proper operation on non-latin chars (to compile into different encoding)... Thanks for your quick response |
Hello, mbojanks,
I've tested Apatar on Custom Table and successfully previewed Cyrillic characters. However, we were experiencing problems with MS Access conversion previously, that's true. The characters were replaced with ??? symbols, as you noted above.
I'm redirecting this issue to Apatar developers so that they could have a look and decide what to do. You can also contact Ludmila, VP of Business Development, via ludmila.r@apatar.com.
Have a great week-and and give our regards to Beograd! =) _________________
Alex Khizhnyak
Apatar Evangelist
Blog on Data Integration and Open Source
Contact Apatar Team |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Sat Aug 16, 2008 10:25 am Post subject: |
|
|
Thank you Alex for your support and for regards as well. I don't quite understand what sort of table you tested on (plain text or something?) when you had Cyrillic characters previewed correctly. What about MySQL tables? I also have the question mark issue there. I still hope it will be solved soon, because the Apatar project deserves ultimate success in its idea of connecting and transforming data from anywhere to everywhere. I 'm sure Apatar developers will manage to find the solution.
Kindest regards, |
|
| Back to top |
|
 |
alex Apatar Team Member

Joined: 30 Mar 2007 Posts: 464
|
Posted: Mon Aug 25, 2008 3:56 pm Post subject: |
|
|
| mbojanks wrote: | Thank you Alex for your support and for regards as well. I don't quite understand what sort of table you tested on (plain text or something?) when you had Cyrillic characters previewed correctly. What about MySQL tables? I also have the question mark issue there. I still hope it will be solved soon, because the Apatar project deserves ultimate success in its idea of connecting and transforming data from anywhere to everywhere. I 'm sure Apatar developers will manage to find the solution.
Kindest regards, |
Hello, mbojanks,
It seems like you've found a bug here (in the MS Access connector). Apatar developers will start working on it during the next week as soon as our main developer returns from his vacations. =)
I encourage you to write directly to Ludmila to tell her about the same problem in MySQL.. _________________
Alex Khizhnyak
Apatar Evangelist
Blog on Data Integration and Open Source
Contact Apatar Team |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Mon Aug 25, 2008 9:42 pm Post subject: |
|
|
Hello, Alex. I hope the main developer will start his/her new working season with success in solving this bug. Perhaps s/he should analize MySQL connector as well. I wish you all the best to all of you in Apatar.
Regards,
Bojan |
|
| Back to top |
|
 |
Michael

Joined: 26 Aug 2008 Posts: 22
|
Posted: Mon Sep 01, 2008 3:35 pm Post subject: |
|
|
| mbojanks wrote: | Hello, Alex. I hope the main developer will start his/her new working season with success in solving this bug. Perhaps s/he should analize MySQL connector as well. I wish you all the best to all of you in Apatar.
Regards,
Bojan |
Hi mbojanks,
The issue you have desribed seems to persist when different character encodings are used by the two systems, your local computer and the database. If the encodings match, the problem is unlikely to appear. In the future versions of Apatar, our developers consider either implementing a button to set the encoding manually, or making Apatar independent from character encoding.
A solution feasible at the moment is to configure the encoding either on your computer, or within the db. _________________ Michael Fedotov
Apatar Evangelist
Contact Apatar Team |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Mon Sep 01, 2008 8:45 pm Post subject: |
|
|
When I tested, both databases (source and target) were on the same machine and the question mark issue occurred. Those were both .mdb files from my local computer. If I can do anything to provide you with more information, be free to ask me for.
Thank you for your effort in solving this problem. I am sure you will manage to solve it and make Apatar even more versatile tool...
Speaking of versatility, what about support for EDI FACT format that some commercial products provide (Softshare Delta for instance)? |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Mon Sep 01, 2008 8:49 pm Post subject: |
|
|
OK, now, I see your point. I 'll try to set Serbian Cyrillic encoding on my computer with Apatar window in focus and then try the testing transformation again.
Thank you, Michael, for providing this solution. |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Mon Sep 01, 2008 9:37 pm Post subject: |
|
|
... and here is the result:
I clicked on my bottom-right corner SR button while Apatar window in focus and make Serbian Cyrillic active keyboard, then I clicked on Preview results for output MS Access connector (source table has 840 records of places - MESTO=PLACE; target table is also MESTO with no records) and obtained this in my Preview window:
Progress:
com.altoros.octoslave.msaccess.MsAccessNode created.
Records Processed 0
Start Reading from MESTO
Records Processed 840
com.altoros.octoslave.msaccess.MsAccessNode created.
Records Processed 0
Start Reading from MESTO
Records Processed 840
com.altoros.octoslave.transform.TransformNode created.
Records Processed 0
com.altoros.octoslave.msaccess.MsAccessNode created.
Records Processed 0
Start writing to MESTO
Insert Mode
Records Processed 676
[Microsoft][ODBC Microsoft Access Driver] Cannot open any more tables.
Start Reading from MESTO
Records Processed 3380
Finish
//end of Preview window data
Results previewed: 2704 records with ???? instead of Cyrillic chars
2704=4*676→ maybe it means something
There is also the following issue: Nothing happens in the target MESTO table (remains empty), when I click Run and the same Progress: is written
You would know better this ODBC Driver error is all about, it could be the cause of not performing the transformation when Run was clicked... and why proccessing all this for four times
The 677th record is nothing special (Томашевац - if you can see it in Cyrillic)
Also, my JRE Version is 1.6.0_07, as displayed in DEbug Console, but I also have 1.5.0_15 installed
I hope these details can help you locate a problem.
Regards,
Bojan |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Mon Sep 01, 2008 9:39 pm Post subject: |
|
|
| Naturally, MESTO source and target tables are in different .mdb files... |
|
| Back to top |
|
 |
Michael

Joined: 26 Aug 2008 Posts: 22
|
Posted: Tue Sep 02, 2008 11:35 am Post subject: |
|
|
Hi Bojan,
Are you using an English or Serbian version of Windows? If you have an English Windows version, try installing Serbian character encodings via Control Panel>Regional and Language Options>Advanced. _________________ Michael Fedotov
Apatar Evangelist
Contact Apatar Team |
|
| Back to top |
|
 |
mbojanks

Joined: 06 Aug 2008 Posts: 10
|
Posted: Wed Sep 03, 2008 6:26 pm Post subject: |
|
|
I use English Windows. I had problems with loading the operating system when I tried Language for non-Unicode programs to be Serbian (Cyrillic). I have Serbian language installed for keyboard layout and all Cyrillic Code page conversion tables checked.
I performed another test: included just five records in the source table and executed Preview results on INPUT CONNECTOR. I concluded from the results that DATA ARE INITIALLY NOT SEEN PROPERLY, even with Serbian Latin chars (for instance, š is seen as љ, Đ as P, Ć as C, and all Cyrillic chars as question marks). Transformed chars are not seemed to be a problem, EXCEPT FOR RUN NOT WORKING - output table remains empty!
I really wish you to solve these problems, because it would bring a very good and useful software to entire community.
Regards,
Bojan |
|
| Back to top |
|
 |
rtest
Joined: 16 Dec 2008 Posts: 71
|
Posted: Wed Sep 09, 2009 8:50 am Post subject: |
|
|
I am also facing the same problem with "Thai" language characters.
Any code change done in resolution of this problem.
Regards,
Rohit |
|
| Back to top |
|
 |
|