Github user riknoll commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/143#issuecomment-161744445
@purplecabbage @sencenan I agree that getting the file path out of a
content URI is becoming too convoluted to be sustainable. Getting the
InputStream from the ContentResolver comes with it's own awkwardness as well,
however, due to Android's [ExifInterface
class](http://developer.android.com/reference/android/media/ExifInterface.html).
We use that class to extract the EXIF data and preserve it as we modify the
image (for quality, orientation, etc.). Unfortunately, it does not take in an
InputSteam and so we would have to find/code a new EXIF reader or do something
weird with writing the image twice (copy image to temp location -> read EXIF
from temp image -> overwrite temp image with modified image -> return temp
image URI). Thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
