Package import problem - community.ez.no

Wednesday 11 August 2004 10:37:44 pm - 3 replies

Modified on Wednesday 11 August 2004 10:38:36 pm by Zoltan Szabo

3 replies

Author	Message
Paul Forsyth	Wednesday 11 August 2004 11:52:15 pm Are you using a utf-8 ready database, such as mysql 4.1? paul -- http://www.visionwt.com
Jan Borsodi	Thursday 12 August 2004 12:33:46 am Do you mean it skipped those characters or did it replace it with some other characters? Could you try to unpack the package using the tar command? tar xvfz mypackage.ezpkg Then look at the xml files, do they contain those characters verbatim, or are they encoded (UTF-8)? -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Zoltan Szabo	Saturday 21 August 2004 11:00:33 pm I use postgresql-7.4.2 database whith latin2 (iso-8859-2) charset. I tried to work with utf-8 encoded database, but it gave errors in some cases. This latin2 runs well eZp3.4.1, except this package import feature. In the untared files there are unicode characters. The content objects fail to be correctly imported, BUT the CLASS DEFINITIONS are FINE - the imported "nice" names are keeping the accented characters (they are also unicode chars in the untared filesystem). I recoded the untarred files (with a recode UTF-8..l2 myfile command), but after import the "nice" characters are forgotten.

Author

Message

Paul Forsyth

Wednesday 11 August 2004 11:52:15 pm

Are you using a utf-8 ready database, such as mysql 4.1?

paul

--
http://www.visionwt.com

Jan Borsodi

Thursday 12 August 2004 12:33:46 am

Do you mean it skipped those characters or did it replace it with some other characters?

Could you try to unpack the package using the tar command?

tar xvfz mypackage.ezpkg

Then look at the xml files, do they contain those characters verbatim, or are they encoded (UTF-8)?

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Zoltan Szabo

Saturday 21 August 2004 11:00:33 pm

I use postgresql-7.4.2 database whith latin2 (iso-8859-2) charset.
I tried to work with utf-8 encoded database, but it gave errors in some cases.
This latin2 runs well eZp3.4.1, except this package import feature.

In the untared files there are unicode characters.

The content objects fail to be correctly imported, BUT the CLASS DEFINITIONS are FINE - the imported "nice" names are keeping the accented characters (they are also unicode chars in the untared filesystem).

I recoded the untarred files (with a recode UTF-8..l2 myfile command), but after import the "nice" characters are forgotten.

You must be logged in to post messages in this topic!