Bug 235269 - Import cyrilic (non-ASCII probably) history from pidgin txt logs not working.
Summary: Import cyrilic (non-ASCII probably) history from pidgin txt logs not working.
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-24 15:24 UTC by Fest
Modified: 2023-01-29 05:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fest 2010-04-24 15:24:41 UTC
Version:            (using KDE 4.4.2)
Installed from:    Gentoo Packages

When trying to import history from pidgin txt logs everything going fine, till i get to russian contacts.

First of all i get "Did you use "ÐлÑ" as nickname in history?" message.
Funny but in parsed history dialog, name appears as it should be. But in right window log i get such messages:
"23:50:29 Fest: ÑÑ Ð·Ð½Ð°ÐµÑ Ð°ÑабÑкий?"

Txt files encoding is unicode (UTF-8). Also Import cyrilic history from pidgin HTML logs work perfect, so it's seem's txt parser has problem with non-ASCII symbols.
Comment 1 Sampath 2010-11-28 12:51:04 UTC
The most common warning I get when importing pidgin logs to kopete is 

    WARNING: Cannot parse date "(02:44:50  IST)". You may want to edit the file containing this date manually. (Example recognized date strings: "05/31/2008 15:24:30".)
    WARNING: Cannot parse date "(02:45:06  IST)". You may want to edit the file containing this date manually. (Example recognized date strings: "05/31/2008 15:24:30".)


The importing doesn't work as expected. All the files get appended to one file, there is no importance given to date and time I guess and moreover I got only 2 logs when there are some 80+ test logs when importing
Comment 2 Andrew Crouthamel 2018-11-05 03:14:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-17 04:59:15 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-15 05:48:52 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-30 05:22:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Sampath 2022-12-30 18:04:01 UTC
Its been like 8 years after bug report so many things changed and now I dont even use google talk and Kopete/Pidgin. Just to test this bug now, I tried to install Kopete and do the importing stuff but I cannot login into Google talk. The boat has been sailed and now this bug and its related stuff is irrelevant to me. I take that other people in this bug report also has similar views and I think we can close this bug.
Comment 7 Bug Janitor Service 2023-01-14 05:11:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-29 05:06:52 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!