Guten Tag Javier Lafuente,
am Dienstag, 12. Dezember 2006 um 19:03 schrieben Sie:
> But my problem is that I work in UTF-8... What have I need to add?
> Something like?
$request->>{ original_log_message } = $original_log_message;
$request->>{ original_log_message } = decode("UTF-8", $request->{
original_log_message });
> does this make sense?
I would have tried the same but the point is that Perl already handles
all intern Strings as UTF-8 encoded calues. The problem was that
everything which was read bei SCMBug from the console was internally
not handled as a proper Perl-String, this issue is adressed by the
decode-line which decodes "anything" under specification into a proper
Perl string.
> Am I decoding from UTF-8 to UTF-8???
Thats what I would think, the encoding of the resulting Perl string
and whatever SCMBug used before should be the same. The only
difference is that with the decode-line you cane be sure that Perl
handles the data internally as a proper Perl string and not just as a
bunch of characters. This is important for any kind of conversion
lateron. Kristis link should explain the difference, I have forgotten
to attach that one, too. :-(
There's one more thing to consider: Maybe Bugzilla handles UTF-8
encoding before writing it to the database in another way than RT. In
my oppinion Bugzilla is directly sending whatever comes from within
Perl, because it's assumed as UTF-8 encoded, to the database. That was
the problem with SCMBug, because it sends the formerly CP850-encoded
String from my console directly to AppendComment from Bugzilla which
either sends it directly to the database.
RTs behaviour may be completely different.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
eMail [EMAIL PROTECTED]
Telefon Potsdam...0331-743881-0
Telefon Mobil.....0178-8 9468-04
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
