[Bug 61254] New: tp_message_to_text() does not flag delivery reports with bodies as Non_Text_Content

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=61254

          Priority: medium
            Bug ID: 61254
          Assignee: telepathy-bugs at lists.freedesktop.org
            Blocks: 43166
           Summary: tp_message_to_text() does not flag delivery reports
                    with bodies as Non_Text_Content
        QA Contact: telepathy-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: will.thompson at collabora.co.uk
          Hardware: Other
            Status: NEW
           Version: git master
         Component: tp-glib
           Product: Telepathy

>From bug 43166:

> > Unfortunately it exposes a
> > tp-glib bug/issue: the legacy Received signal gets the text of the error
> > from the server (which seems fine) but loses the Non_Text_Content flag
> > (because there is text content).
> 
> Hmm. I think the solution to this is probably that Message_Type_Delivery_Report
> should trigger Non_Text_Content? In my original draft of DeliveryReports, they
> would have had { 'interface': '...DeliveryReports' } in the header, which I
> think does trigger Non_Text_Content, but that was lost when delivery reports
> became a core part of Messages in a later draft.
> 
> This might be a bit more significant than it looks, because on the client side,
> telepathy-glib Messages clients use the same code to make tp_message_to_text()
> output Non_Text_Content if necessary.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.