ThunderSync 2 Erratum

Today I found a small typo in a file writing subroutine of ThunderSync 2, causing a fallback writing command to fail. No data is lost, but under certain conditions the synchronisation process exits prematurely.

These conditions are met when the user has chosen a non-Unicode export charset and wants to export data containing characters outside the charset.

Workaround: If you encounter this error (indicated by entries in the error console), switch to Unicode as export charset. Without the typo, ThunderSync would use Unicode automatically because a conversion into your preferred charset is not possible.

I’ll fix this in March.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s