The special characters you have on the flags breaks SVN post-commit functions.

Warning: 'post-commit' hook failed with error output:
svn: Can't convert string from 'UTF-8' to native encoding:
svn: sites/all/modules/gtranslate_links/flags/00_serbian_c?\209?\128?\208?\191?\209?\129?\208?\186?\208?\184_sr.png

You really need to replace those characters with friendly characters.

Comments

blinkingtwelve’s picture

blinkingtwelve commented
Assigned: Unassigned » blinkingtwelve
Priority: Critical » Normal
Status: Active » Closed (fixed)

1) They're not special or invalid. They're UTF-8. There are billions of people who use an alfabet other then our Latin one, are their books 'invalid'? Kidding ;-)

2) Generally, if you have problems with SVN, you should file a bug over there, not here. Nowhere does this module promise you SVN compatibility (it seems perfectly compatible, though, it's your setup that needs adjustment to handle UTF-8).

3) I have had no problems putting committing and checking out from CVS, and is looks like Subversion, like any other modern piece of software, is able to outpput UTF-8 just fine — provided you setup your gear right, which seems quite simple (just set an environment variable) but there may be more to it. Do some googling yourself if you can't get it to work with the previous link. You need to make sure your environment is UTF-8 ready, that includes the environment of your post-commit functions.

4) UTF-8 filenames are going to go in the near future due to #592052: User interface design. If you don't succeed in upgrading your gear to be UTF-8 compatible, you could just sit tight and wait.

5) 'Critical' is a priority you use when a module eats a database. For something that nondestructively impacts only you and your third-party software (SVN), use the priority field accordingly.

Thanks for the bug report, though. It counts: if there's many people still running UTF-8 incompatible setups that may be a reason to simplify things. But then they may never discover Unicode ;-)