savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-help-public] [sr #105528] Deal with encoding issues in log_acc


From: Sylvain Beucler
Subject: [Savannah-help-public] [sr #105528] Deal with encoding issues in log_accum
Date: Mon, 14 Jan 2008 18:15:01 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Follow-up Comment #8, sr #105528 (project administration):

> Yavor asked for progress on this one.

As far as I'm concerned I didn't progress. We would welcome more information
about how CVS deals with commit messages:
- does it add any encoding metadata? (e.g. the locale in use at commit time,
if cvs is used from the command line)
- is the encoding considered ASCII?
- how well do the encoding "auto-guess" libraries can perform on such small
messages?
- how practical would it be to add a charset marker at the beginning of each
commit message?

As for the content of the message, this is probably more difficult - first
the diff needs to be independant, for example an attachment. Then the encoding
is almost certainly unknown to CVS, because any kind of text file can be
versioned independently of its charset. Probably only an encoding "auto-guess"
method would work.

If anyone can research about this, we use log_accum and commit_prep from the
contrib/ directory in project CVS.
http://cvs.sv.gnu.org/viewvc/ccvs/contrib/?root=cvs

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?105528>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]