Thank you for the information. > There is a chance however that some 3rd party app allows users to freely > modify that title or that users keep image files on their harddrives without > any extensions.
I see, then we won't check the <title> element because it' not a perfect solution. We treat this problem as a limitation until the root problem is fixed. Regards, Hiroyuki Kurokawa On Jul 31, 1:08 am, Detlev Schwabe <dschw...@google.com> wrote: > Sorry for the delay in approving your messages (this is a moderated group > and I was out for a few days). > Yes, you can use the <title> element to implement a workaround for the issue > for now. > There is a chance however that some 3rd party app allows users to freely > modify that title or that users keep image files on their harddrives without > any extensions. > I guess you would just have to either skip this image entirely or bet on the > very high probability that it is a JPEG image and not something else. > > 2010/7/28 Hiroyuki Kurokawa <kurok...@gmail.com> > > > > > Hi, > > > Thank you for the reply. > > > We are developing an installed application and not using a web browser. > > Our application fails to show the image if a PNG stream is returned for > > a JPG feed because the codec library is selected based on the mime-type > > value in the type attribute of <media:content> element. > > > > Note that you can still check the <title> element of the photo entry to > > > determine the original filename of the uploaded photo (and if needed, > > could > > > replace the last part of the image URL with the title as a workaround). > > > You mean that the <title> element of photo always contains the correct > > extension such as ".jpg" or ".png". If so, our application can avoid this > > bug. > > We will consider referring the <title> element instead of the > > media:cont...@type > > attribute. > > > Regards, > > > 2010/7/28 Detlev Schwabe <dschw...@google.com>: > > > Thanks for your bug report. I was able to confirm the issue. > > > Although this is clearly a bug in our search component, I was wondering > > what > > > type of issues your are experiencing because of this? The incorrect > > filename > > > shouldn't really have a direct impact on lets say, displaying the image > > in a > > > web browser. > > > Note that you can still check the <title> element of the photo entry to > > > determine the original filename of the uploaded photo (and if needed, > > could > > > replace the last part of the image URL with the title as a workaround). > > > > On Mon, Jul 26, 2010 at 6:49 PM, pxi05...@nifty.com <kurok...@gmail.com> > > > wrote: > > > >> I posted this defect on gdata-issues but no one replies for now. > > >>http://code.google.com/p/gdata-issues/issues/detail?id=2223 > > >> I guess there must be a bug on community search feed. > > > >> Does anyone have any solution or workaround? > > > >> ------------------------------------------------------------- > > >> Name of API affected: > > >> Picasa Web Albums Data API > > > >> Issue summary: > > >> The PNG stream is returned for JPG URL in a feed. > > >> This seems to happen only for a feed of community search with keyword. > > > >> Steps to reproduce issue: > > >> 1. login to Picasa. > > >> NOTE: you will get different search result if you does not login. > > >> 2. get a feed by > > >http://picasaweb.google.com/data/feed/api/all?q=PSP&start-index=1&max... > > >> 3. get photo stream by > > >http://lh3.ggpht.com/_9nQl7GkZqiE/SXmrN9_-R0I/AAAAAAAACrs/n5VxKvcKCNs... > > >> which is 33th photo of returned feed. > > > >> Expected output: > > >> PNG URL is returned for PNG photo. > > >> OR JPG stream is returned for JPG feed. > > > >> Actual results: > > >> PNG stream is given for JPG feed. > > > >> Notes: > > >> If I get an entry data by > > >http://picasaweb.google.com/data/feed/api/user/mundo.dopsp/albumid/52... > > >> , > > >> then PNG URL is described in it. > > > >> -- > > >> You received this message because you are subscribed to the Google > > Groups > > >> "Google Picasa Web Albums API" group. > > >> To post to this group, send email to > > >> google-picasa-data-...@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> google-picasa-data-api+unsubscr...@googlegroups.com<google-picasa-data-api% > > >> 2bunsubscr...@googlegroups.com> > > . > > >> For more options, visit this group at > > >>http://groups.google.com/group/google-picasa-data-api?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google Picasa Web Albums API" group. > > > To post to this group, send email to > > > google-picasa-data-...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > google-picasa-data-api+unsubscr...@googlegroups.com<google-picasa-data-api% > > > 2bunsubscr...@googlegroups.com> > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-picasa-data-api?hl=en. > > > -- > > 黒川裕之 > > kurok...@gmail.com > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Picasa Web Albums API" group. > > To post to this group, send email to > > google-picasa-data-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-picasa-data-api+unsubscr...@googlegroups.com<google-picasa-data-api% > > 2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-picasa-data-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" group. To post to this group, send email to google-picasa-data-...@googlegroups.com. To unsubscribe from this group, send email to google-picasa-data-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-picasa-data-api?hl=en.
