Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

problem symbol €

G

giuagio last edited by rfc2822

Hello, the app server from Memotoo.com an error when I synchronize. It does not synchronize the symbol €, but in its place put the strange symbols. How can I fix it? thank you so much.
Reply Quote 0
1 Reply Last reply
rfc2822 developer last edited by

Hello,

DAVdroid fully supports UTF-8. This must be a server problem, please contact your service provider.
Reply Quote 0
1 Reply Last reply

2
Posts

963
Views

Maybe you're interested in these topics?

[iCloud] RECURRENCE-ID for exceptions of recurring all-day events are DATE-TIMEs instead of DATEs
Specific server/service configuration • 3rd-party issue icloud • • rfc2822

1

0
Votes

1
Posts

116
Views

For reference and transparency: We have created this report on Apple Bug Reporter on 6 Aug 2015 here: https://bugreport.apple.com/web/?problemID=22169036 Summary: RECURRENCE-ID for exceptions of recurring all-day events should be of type VALUE=DATE, but they have VALUE=DATE-TIME. Steps to Reproduce: Create a recurring all-day event (for instance, daily for 10 days). Create an exception on a particular date, for instance change the title (SUMMARY) Expected Results: # master event: DTSTART;VALUE=DATE:20150804 # exception: RECURRENCE-ID;VALUE=DATE:20150805 Actual Results: # master event: DTSTART;VALUE=DATE:20150804 # exception: RECURRENCE-ID:20150805T000000 As you can see, the RECURRENCE-ID is for VALUE=DATE-TIME, while the original event is of type VALUE=DATE. This causes some clients to ignore the exception and/or add an additional event instead of using this event as an exception. Notes: http://tools.ietf.org/html/rfc5545#section-3.8.4.4 If the value of the “DTSTART” property is a DATE type value, then the value MUST be the calendar date for the recurrence instance. Configuration:
S

Can't create account with IPv6 address
DAVx⁵ • 3rd-party issue bug • • Sheldor

5

0
Votes

5
Posts

1564
Views

Turns out that Android’s Uri class doesn’t understand IPv6 literals. It returns Error parsing port string. java.lang.NumberFormatException: Invalid int: "2::3]" when calling it for http://[2a02:2::3]/test because it interprets everything before the first : as host name, and everything else as port number (quality crafted by Google). Seems like we have to wrap the the check into a real Java URI.
[iCloud] CardDAV: Structured name (N) is used for contact group titles (instead of FN)
Specific server/service configuration • 3rd-party issue icloud • • rfc2822

1

0
Votes

1
Posts

146
Views

For reference and transparency: We have created this report on Apple Bug Reporter on 8 June 2016 here: https://bugreport.apple.com/web/?problemID=26696591 Summary: If you upload a contact group (X-ADDRESSBOOKSERVER-KIND: group), iCloud insists that the VCard must have a FN and a N (as specified in VCard 3). iCloud seems to take the group name from the structured name (N) instead of the formatted name (FN). Additionally, it doesn’t only take the first component of the structured name, but the whole line as a string (which should not happen). N represents the structured name and these representations mean the same: N:Family Name,,,, N:Family Name When a group with the first version, iCloud will display “Family Name,” as group name. Steps to Reproduce: Upload (PUT) a contact group with these properties: N:Family Name,,,, N:Family Name Expected Results: iCloud will show a group “Family Name,” Actual Results: iCloud should show a group “Family Name” (by FN, not N). Version: iCloud on 8 Jun 2016 Notes: This problem was found while developing DAVdroid. Configuration: – Update from 12 Oct 2018: Typo in steps to reproduce. Should be: N:Family Name,,,, FN:Family Name
J

Invalid icalendar file entry triggers DAVDroid exception report
DAVx⁵ • 3rd-party issue • • jelmer

4

0
Votes

4
Posts

902
Views

@jelmer Theoretically, yes. But this would make the sync interactive and completely turn around how DAVdroid is intended to work (in the background, without user interaction). I guess the best option is to repair the event manually. Also, servers shouldn’t send invalid events, so maybe they could be repaired there. Or better yet, fix the client which has created the event so that it doesn’t create invalid events.
A

Calendar.mail.ru not sync
DAVx⁵ • 3rd-party issue • • AutoImport-covrom

11

0
Votes

11
Posts

4078
Views

Seems to be working now (latest DAVdroid version). We will add mail.ru to our list of tested services.

1 / 1

problem symbol €

Maybe you're interested in these topics?

[iCloud] RECURRENCE-ID for exceptions of recurring all-day events are DATE-TIMEs instead of DATEs Specific server/service configuration • 3rd-party issue icloud • • rfc2822

Can't create account with IPv6 address DAVx⁵ • 3rd-party issue bug • • Sheldor

[iCloud] CardDAV: Structured name (N) is used for contact group titles (instead of FN) Specific server/service configuration • 3rd-party issue icloud • • rfc2822

Invalid icalendar file entry triggers DAVDroid exception report DAVx⁵ • 3rd-party issue • • jelmer

Calendar.mail.ru not sync DAVx⁵ • 3rd-party issue • • AutoImport-covrom

[iCloud] RECURRENCE-ID for exceptions of recurring all-day events are DATE-TIMEs instead of DATEs
Specific server/service configuration • 3rd-party issue icloud • • rfc2822

Can't create account with IPv6 address
DAVx⁵ • 3rd-party issue bug • • Sheldor

[iCloud] CardDAV: Structured name (N) is used for contact group titles (instead of FN)
Specific server/service configuration • 3rd-party issue icloud • • rfc2822

Invalid icalendar file entry triggers DAVDroid exception report
DAVx⁵ • 3rd-party issue • • jelmer

Calendar.mail.ru not sync
DAVx⁵ • 3rd-party issue • • AutoImport-covrom