Have an issue updating configurations from the svn repository due to
svn: Can't convert string from 'UTF-8' to native encoding:
svn: configuration/citewfs-1.1/featureTypes/sf_Entit?\195?\169G?\195?\169n?\195?
\169rique
because of
https://svn.codehaus.org/geoserver/trunk/configuration/citewfs-1.1/featureTypes/sf_EntitéGénérique
unless I change my locale
however, there is no mention of this issue here:
http://docs.codehaus.org/display/GEOSDOC/2+Subversion+conventions
and the SVN book says:
"The solution is either to set your locale to something which /can/ represent the incoming UTF-8 data, or to change the filename or log message in the repository. (And don't forget to slap your collaborator's hand—projects should decide on common languages ahead of time, so that all participants are using the same locale.)"
what is the recommendation here?
Rob Atkinson
Hi Rob,
This is something i have been meaning to clean up since I don't think we can require developers have a utf8 locale. I needed to add the file as is for wfs 1.1 cite. So i think for now if you could just change your locale that would be good for now but I think long term we want to resolve this so that we don't have to store the file with special characters in it.
-Justin
Rob Atkinson wrote:
Have an issue updating configurations from the svn repository due to
svn: Can't convert string from 'UTF-8' to native encoding:
svn: configuration/citewfs-1.1/featureTypes/sf_Entit?\195?\169G?\195?\169n?\195?
\169rique
because of
https://svn.codehaus.org/geoserver/trunk/configuration/citewfs-1.1/featureTypes/sf_EntitéGénérique
unless I change my locale
however, there is no mention of this issue here:
http://docs.codehaus.org/display/GEOSDOC/2+Subversion+conventions
and the SVN book says:
"The solution is either to set your locale to something which /can/ represent the incoming UTF-8 data, or to change the filename or log message in the repository. (And don't forget to slap your collaborator's hand—projects should decide on common languages ahead of time, so that all participants are using the same locale.)"
what is the recommendation here?
Rob Atkinson
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira wrote:
Hi Rob,
This is something i have been meaning to clean up since I don't think we can require developers have a utf8 locale. I needed to add the file as is for wfs 1.1 cite. So i think for now if you could just change your locale that would be good for now but I think long term we want to resolve this so that we don't have to store the file with special characters in it.
Its useful to test behaviour under different locales, but we need a clue as to the locale of the configuration.
Perhaps we shoud arrange configs under
configuration/ = utf8 (by default)
configuration/localespecific/<locale>/<myconfig>
so at least its obvious what is what, and what locale you need to support to run it.
it would be better still if we could stop SVN from blowing up on the non-supported configs - but I dont know how to achive that.
Rob
-Justin
Rob Atkinson wrote:
Have an issue updating configurations from the svn repository due to
svn: Can't convert string from 'UTF-8' to native encoding:
svn: configuration/citewfs-1.1/featureTypes/sf_Entit?\195?\169G?\195?\169n?\195?
\169rique
because of
https://svn.codehaus.org/geoserver/trunk/configuration/citewfs-1.1/featureTypes/sf_EntitéGénérique
unless I change my locale
however, there is no mention of this issue here:
http://docs.codehaus.org/display/GEOSDOC/2+Subversion+conventions
and the SVN book says:
"The solution is either to set your locale to something which /can/ represent the incoming UTF-8 data, or to change the filename or log message in the repository. (And don't forget to slap your collaborator's hand—projects should decide on common languages ahead of time, so that all participants are using the same locale.)"
what is the recommendation here?
Rob Atkinson
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel