B Smith-Mannschott wrote on Wed, Aug 25, 2010 at 07:54:26 +0200: > On Tue, Aug 24, 2010 at 21:19, Ivan Cenov <i_ce...@botevgrad.com> wrote: > > > Hello, > > > > This is my first post in this list. I was pointed to post here in another > > thread > > ViewVC site (http://viewvc.tigris.org/issues/show_bug.cgi?id=11). > > > > The original reason was that ViewVC is unable to show correctly text files > > that contain Cyrillic characters (character set windows-1251). (The same > > issue > > is related for Western Europe's characters too.) > > People told me that ViewVC cannot do this because it lacks of encoding > > information. This information should come from Subversion and > > Subversion could have this information if the users have supplied it into > > Subversion. > > The last posts in above mentioned thread give more information about the > > problem. > > > > As I understood, information about character encoding may be supplied as > > svn: property, say, svn:encoding encoding_type. Par example: > > svn:encoding windows-1251. > > > > So, are there any intentions among the Subversion developers and users to > > be defined > > such property? Would it be reliable way for this task? > > If there is an issue about this problem, what is its priority? > > > > > The property svn:mime-type carries charset information as an additional > field: > > $ svn propset svn:mime-type "text/plain;charset=Windows-1251" file1.txt > file2.txt ... >
Ben, does svnbook document this syntax (and when to use it)? (or the "$Keyword::$" syntax, while I'm at it) > // ben