[rt-users] converting from gnats to RT3

[Palle Girgensohn]

--On onsdag, november 05, 2003 17.27.15 -0500 Jesse Vincent 
<jesse at bestpractical.com> wrote:

>
>
>
> On Wed, Nov 05, 2003 at 11:18:37PM +0100, Palle Girgensohn wrote:
>> Thanks, interesting approach. :)
>>
>> About the Unicode conversion, since I use PostgreSQL, all I need to do
>> is  tell Postgresql "set client_encoding = 'LATIN1'"  and I can insert
>> iso8859-1 characters into a unicode database; they will be converted
>> on-the-fly. Only, I cannot find a way to tell anything to postgresql
>> directly :)
>
> Be very careful with that approach. If you've got unicode dat a in the
> database that has a MIME header that says it's latin1, I expect you're
> going to hurt yourself.
> 	Jesse

Aha. Well, I get the following error in the postgresql log:

query: INSERT INTO Tickets (Creator, Due, Told, Status, EffectiveId, 
LastUpdatedBy, Resolved, Type, TimeWorked, LastUpdated, Subject, Queue, 
FinalPriority, id, Owner, InitialPriority, Created, Priority) VALUES ('1', 
NULL, NULL, 'resolved', 1489, '1', NULL, 'ticket', '0', NULL, 'Går ej att 
godkänna en.', '3', NULL, 1489, '10', NULL, NULL, NULL)

ERROR:  Invalid UNICODE character sequence found (0xe57220)

So, this subject has to be converted to unicode, right?

Perhaps the best approach is to convert via RT2? It just sounds a bit odd...

Regards,
Palle

>>
>> Palle
>>
>>
>> --On onsdag, november 05, 2003 20.42.54 +0300 "Ruslan U. Zakirov"
>> <cubic at acronis.ru> wrote:
>>
>> > Palle Girgensohn wrote:
>> >> Hi!
>> >>
>> >> I want to migrate my GNATS database into RT. I'm just now looking at
>> >> the import-gnats script from the cvs module rt-addons. It is old,
>> >> written for RT2 and just does not work. I've been doing a bit of
>> >> rewriting, but it seems the script does not do basic stuff like
>> >> creating the responsible users before importing, or convert to
>> >> Unicode before inserting into database. Does anyone have an updated
>> >> script for this task, one that works?
>> >>
>> >> If not, I need a hint: Can I tell RT that my strings are ISO-8859-1
>> >> when I use $Ticket->Import()
>> > You can try next trick:
>> > 1) Convert GNATS to rt2 with that script
>> > 2) Convert rt2 to rt3
>> > :)
>> >
>> > If you want write GNATS to rt3 import tool then my suggestions are:
>> > 1) rt2-to-rt3 have two parts rt2-to-filedump and filedump-to-rt3 so you
>> > have to write GNATS-to-rt3_filedump only. 2) rt2 don't have utf support
>> > so rt2-to-filedump do all crossencoding convertions.
>> >
>> > I hope this would help.
>> >	Good luck. Ruslan.
>> >
>> >>
>> >> Thanks
>> >> Palle
>> >>
>> >> _______________________________________________
>> >> rt-users mailing list
>> >> rt-users at lists.fsck.com
>> >> http://lists.fsck.com/mailman/listinfo/rt-users
>> >>
>> >> Have you read the FAQ? The RT FAQ Manager lives at
>> >> http://fsck.com/rtfm
>> >
>> >
>>
>>
>>
>>
>> _______________________________________________
>> rt-users mailing list
>> rt-users at lists.fsck.com
>> http://lists.fsck.com/mailman/listinfo/rt-users
>>
>> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
>>
>
> --
> http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.