| Date: Tue, 11 Mar 2003 13:31:45 +0100
| From: Ionel Mugurel Ciobica <[EMAIL PROTECTED]>
| To: [EMAIL PROTECTED]
| Subject: Re: CVS log messages into UTF-8
|[ ... ]
| > > iconv --from-code=ISO-8859-1 --to-code=UTF-8
|[ ... ]
| > Yeh, but that would also convert the source and binary data inside the
| > RCS file, not only the log messages. :) The script has to know about
| > the @ and @@ sections inside the file so nothing else but the messages
| > are converted.
|
| find . -name '*.log' -exec iconv --from-code=ISO-8859-1 --to-code=UTF-8 {} \;
( what `*.log' files? how are these related to the `*,v' files in
the original question, or which the reply above is talking about?
and the original question wanted the converted messages to stay in
the files, not be concatenated to stdout .... ;-) )
I suspect any attempt to modify the `*,v' files directly is doomed.
whilst I believe, based on rcsfile(5), that RCS files do not have a
checksum (unlike SCCS `s.*' files), I presume there are other gotchas.
my suggestion is to extract the log message, probably on a revision-
by-revision basis, using rlog(1); iconv(1) the message; and then put
it back as the revision's message using rcs(1). and sorry, no, I do
not know of any pre-existing script which could be used or adopted.
and, of course, the obvious: make d**n certain you have a correct,
readable, up-to-date full backup of your (locked?) repository, safely
stored away from any disaster, before you start with your well-tested
script .....
good luck! cheers,
-blf-
--
«How many surrealists does it take to | Brian Foster Montpellier,
change a lightbulb? Three. One calms | [EMAIL PROTECTED] France
the warthog, and two fill the bathtub | Stop E$$o (ExxonMobile)!
with brightly-colored machine tools.» | http://www.stopesso.com
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
