Summary: | TpLogger does not import pidgin logs for gadugadu accounts | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Julian Sikorski <belegdol> |
Component: | sunshine | Assignee: | Krzysztof Klinikowski <kkszysiu> |
Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | nicolas |
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Julian Sikorski
2011-11-15 03:19:20 UTC
Must be something like the sametimes/meanwhile issues. The problem is most likely that the plugin name is not the protocol name. Telepathy gives the protocol name, but purple logs in a folder with the plugin name. Would be nice to get the complete translation list so we can implement that all at once. Sunshine stores its logs in ~/.local/share/TpLogger/logs/sunshine_gadugadu__3xxxxxxx0/ libpurple in ~/.purple/logs/gadu-gadu/4892178/ hope this helps. I fail at censorship :) (In reply to comment #3) > I fail at censorship :) hehe, that's why I only asked for the dir in .purple/logs ;). So "gadu-gadu", interesting. Yeah, maybe it's the hyphen which is making the difference? Yeah, that could be it! I will talk with Telepathy team how to resolve this. (In reply to comment #6) > Yeah, that could be it! I will talk with Telepathy team how to resolve this. Well the logger stuff is mainly me these days ;) I'm stormer on IRC btw. So what I started yesterday is to build a list purple tp-protocol/purple-icon-name and keep all the one that differs. Then I'll build a map of it and properly translate in the logger pidgin backend. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-sunshine/issues/4. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.