File: UTF8

package info (click to toggle)
fsvs 1.1.16-1
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 2,344 kB
  • ctags: 1,133
  • sloc: ansic: 14,472; sh: 6,793; perl: 631; makefile: 337
file content (31 lines) | stat: -rw-r--r-- 1,142 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

UTF8 in FSVS
------------


Some points which trouble me a bit, and some random thoughts; everything
connected with UTF-8:

- Properties we get from the repository might be easiest stored locally 
  as UTF8, if we don't do anything with them (eg. svn:entry).

- In which properties can be non-ASCII-characters? Does someone define
  user/group names in UTF-8? Can eg. xattr have Unicode characters in them?
	Does that happen in practical usage?

- The currently used properties should be safe. I've never heard from
  non-ASCII groups or users, and the mtime should always be in the same
	format.

- I thought whether I should just do *everything* in UTF-8.
  But that is a performance trade off; on a simple "fsvs status" we'd 
	have to all filenames from the waa-directory. It may not be much work,
	but if it's not necessary ...

- I'd like to have the subversion headers to define a utf8_char *, which
  would (with gcc) be handled distinct from a normal char * ...
	(see linux kernel, include/linux/types.h: #define __bitwise ...)
	But that won't happen, as there's already too much software which relies
	on the current definitions.