Menu
▾
▴
opensync-users
|
From: Michael B. <mic...@cm...> - 2011-01-08 17:02:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 libwbxml 0.10.9 release notes Download: https://sourceforge.net/projects/libwbxml/files/libwbxml/0.10.9/ Major Changes ============= - This is the last 0.10.x release. - This is the last release of libsyncml.so.0. - The next release will break the API because of a bug in the handling of the charcter set. The library must support a default character set which can be specified in the transport meta information. Minor Changes ============= - Added correct default behaviour to parse_charset. If no character set is specified in a WBXML document then UTF-8 is assumed until there is another specification in the transport meta-information. (ticket #52) - Added several tokens for Microsoft ActiveSync v14.0 revision 8.0 (ticket #53). The patch was supplied by Amnon Aaronsohn. - Fixed iconv support (ticket #52) - Fixed wrong WBXML table token for OMA DM DDF (ticket #51) - Fixed locations of variable definitions and replaced strtoull by strtoul (changes from ticket #42 and #50). This fixes some compiler errors from MS VisualStudio 2008 and 9.0. Internal Changes ================ - Fixed integer overflow in opaque data parsing (ticket #54). The patch was supplied by Amnon Aaronsohn. - Fixed unsigned integer overflow (patch from ticket #41) The overflow causes crashs or wrong wbxml messages. - Added support for recursion in wbxml_tree_node_elt_get_from_name (ticket #46) Special thanks goes to Amnon Aaronsohn who provided an update for the Microsoft Active Sync support. Best regards Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0omJcACgkQ2L0ZGCAwWqs0xgCgunG+ZXSHrQIn7FuyFNuVglDW ytsAoOJd5zYTBI6HKmCviupneI2Zg/LN =Q3w/ -----END PGP SIGNATURE----- |
|
From: Emanoil K. <del...@ya...> - 2011-01-08 19:00:02
|
--- On Sat, 1/8/11, Michael Bell <mic...@cm...> wrote:
> From: Michael Bell <mic...@cm...>
> Subject: [Opensync-users] libwbxml 0.10.9
>
> libwbxml 0.10.9 release notes
>
What about the svn version as this is what I'm having currently installed?
regards
|
|
From: Michael B. <mic...@cm...> - 2011-01-10 07:21:45
Attachments:
smime.p7s
|
On 01/08/11 19:59, Emanoil Kotsev wrote: > > --- On Sat, 1/8/11, Michael Bell <mic...@cm...> wrote: >> >> libwbxml 0.10.9 release notes > > What about the svn version as this is what I'm having currently installed? The SVN trunk version is at the moment exactly the same as libwbxml 0.10.9. The next step is to create branch/libwbxml-0.10.x. After this I will add the changes which break the binary compatibility. The handling of the character set must be fixed because of some requirements of Android. They use UTF-16 without a default encoding. This is legal according to the specification but requires that the character set is specified by the transport. This is actually not possible with libwbxml. Additionally I will fix the element names of the Microsoft ActiveSync WBXML table. I will change the SO-naming before I break the binary compatibility. So your local installation should not be damaged by SVN checkouts. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 70135 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Graham C. <g+o...@co...> - 2011-01-10 10:32:06
|
On Monday 10 January 2011 07:21:37 Michael Bell wrote: > The handling of the character set must be fixed because of some > requirements of Android. They use UTF-16 without a default encoding. Nothing to do with OpenSync... Does anyone know if Android has a facility to export vCard/vCalendar files? And, if so, whether those are in UTF-16 as well? If so, I would like to make sure they can be imported into GPE (this is direct import of the file, not using OpenSync). There is an analogous problem as the RFC's do not specify charsets (requiring that the containing transport specifies the charset) -- but when passing text files around, there is no way to specify the charset. So GPE applies a heuristic to guess! If anyone could send me a vCard and/or vCalendar file exported by Android (and containing non-ASCII characters, for example in names or addresses) it would be appreciated. Graham |
|
From: Emanoil K. <del...@ya...> - 2011-01-10 11:51:03
|
Hi, Graham,
--- On Mon, 1/10/11, Graham Cobb <g+o...@co...> wrote:
> From: Graham Cobb <g+o...@co...>
> Michael Bell wrote:
> > The handling of the character set must be fixed
> because of some
> > requirements of Android. They use UTF-16 without a
> default encoding.
>
> Nothing to do with OpenSync... Does anyone know if Android
> has a facility to
> export vCard/vCalendar files? And, if so, whether
> those are in UTF-16 as well?
I do not agree fully here with you. OpenSync has a general problem with charsets as visible from the tickets I've opened recently. And if I would do some more testing I would open more tickets on this subject.
>
> If so, I would like to make sure they can be imported into
> GPE (this is direct
> import of the file, not using OpenSync). There is an
> analogous problem as the
> RFC's do not specify charsets (requiring that the
> containing transport
> specifies the charset) -- but when passing text files
> around, there is no way to
> specify the charset. So GPE applies a heuristic to
> guess!
you can use any type of convertor/editor to get the desired results ;-)
>
> If anyone could send me a vCard and/or vCalendar file
> exported by Android (and
> containing non-ASCII characters, for example in names or
> addresses) it would
> be appreciated.
>
unfortunately I have only symbian and older phones and can not speak for android.
I have noticed something strange in this conjunction. On the phone I can not use i.e. cyryllic or greek input chars (the phone is with german setup - nokia 5530), but I can sync data written in cyrillic (UTF-8) with the phone. Unfortunately I have no successfull test with opensync 0.40 so far
Another issue (also not libwbxml) related (as I reported earlier libwbxml seem to be working fine for contacts and calendar incl. todo and notes) is that some fields are in quted printable or base64 encoded, which breaks OpenSync (merge/sync etc) and I have a mess up with contacts having such data - I think I have opened tickets realted to this in opensync.
regards
|
|
From: Emanoil K. <del...@ya...> - 2011-01-10 11:32:25
|
> The handling of the character set must be fixed because of
> some
> requirements of Android. They use UTF-16 without a default
> encoding.
> This is legal according to the specification but requires
> that the
> character set is specified by the transport. This is
> actually not
> possible with libwbxml.
>From my work with xerces it is not bad idea to use utf-16. In some cases it has more advantages as disadvantages. Why is it not possible to set a default charset in libwbxml. Why should one need anything else except utf?
regards
|
|
From: Michael B. <mic...@cm...> - 2011-01-10 12:44:07
Attachments:
smime.p7s
|
On 01/10/11 12:32, Emanoil Kotsev wrote: > >> The handling of the character set must be fixed because of some >> requirements of Android. They use UTF-16 without a default >> encoding. This is legal according to the specification but >> requires that the character set is specified by the transport. This >> is actually not possible with libwbxml. > > From my work with xerces it is not bad idea to use utf-16. In some > cases it has more advantages as disadvantages. Why is it not possible > to set a default charset in libwbxml. Why should one need anything > else except utf? The problem is that the specification does not define one default encoding. The old specifications WBXML 1.0 or so defined UTF-8 but the new specification WBXML 1.3 defines UTF-8 and UTF-16. So if there is no character set specified which character set should be used? libwbxml uses UTF-8 as default because this is compliant with new and old versions of the specification. Android uses UTF-16 and does not specify the character set in the WBXML document. So the user of the library must set the character set via the interface. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 70135 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Emanoil K. <del...@ya...> - 2011-01-10 14:47:42
|
>
> Android uses UTF-16 and does not specify the character set
> in the WBXML
> document. So the user of the library must set the character
> set via the
> interface.
I do understand now. Do you know if they are using xerces? xerces people argueed for UTF-16. Their argumentation is reasonable.
it seems you have to add an option in the case of libwbxml. Perhaps it will be useful for other devices too - like my nokia. I've seen here that charsets are provided in dependance of the OS version/language you install/use.
I.e. Nokia phones in Bulgaria/Russia etc. would have cyryllic interface supporting cyrillic input (and UTF), German interfaces do not support cyrillic input but can display cyrillic (added in UTF on kde3). The question here for nokia is how would I edit those entries ... but I guess you don't have the answer.
I always say charencoding is Babylon of modern computing - hopefully everything except UTF will be forbidden/unacceptable in near future.
regards
|
|
From: Michael B. <mic...@cm...> - 2011-01-10 16:42:11
Attachments:
smime.p7s
|
On 01/10/11 15:47, Emanoil Kotsev wrote: > >> >> Android uses UTF-16 and does not specify the character set >> in the WBXML >> document. So the user of the library must set the character >> set via the >> interface. > > I do understand now. Do you know if they are using xerces? xerces people argueed for UTF-16. Their argumentation is reasonable. No idea. I just saw a libxml package at the Android repository but they also import many Apache packages. Nevertheless I failed with AndroidManifest.xml (yes, they use the usual xml suffix for binary XML files). I asked on #android if somebody knows details about Androids binary XML but nobody answers until now. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 70135 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X