On Sat, Sep 06, 2014 at 08:24:10AM +0200, Reimar Döffinger wrote:
> On 06.09.2014, at 00:23, wm4 wrote:
> > On Sat, 6 Sep 2014 00:00:10 +0200
> > Michael Niedermayer wrote:
> >
> >> On Thu, Sep 04, 2014 at 10:40:27PM +0200, wm4 wrote:
> >>> ---
> >>> Follows reimar's suggestion for detecting UTF
On 06.09.2014, at 00:23, wm4 wrote:
> On Sat, 6 Sep 2014 00:00:10 +0200
> Michael Niedermayer wrote:
>
>> On Thu, Sep 04, 2014 at 10:40:27PM +0200, wm4 wrote:
>>> ---
>>> Follows reimar's suggestion for detecting UTF-16. If the detection goes
>>> wrong, probing the format won't succeed, so this
On Sat, 6 Sep 2014 00:00:10 +0200
Michael Niedermayer wrote:
> On Thu, Sep 04, 2014 at 10:40:27PM +0200, wm4 wrote:
> > ---
> > Follows reimar's suggestion for detecting UTF-16. If the detection goes
> > wrong, probing the format won't succeed, so this should not break
> > anything.
> >
>
> > I
On Thu, Sep 04, 2014 at 10:40:27PM +0200, wm4 wrote:
> ---
> Follows reimar's suggestion for detecting UTF-16. If the detection goes
> wrong, probing the format won't succeed, so this should not break
> anything.
>
> I didn't use ffio_ensure_seekback), because this apparently reallocates
> the bu
On Thu, Sep 04, 2014 at 10:40:27PM +0200, wm4 wrote:
> ---
> Follows reimar's suggestion for detecting UTF-16. If the detection goes
> wrong, probing the format won't succeed, so this should not break
> anything.
>
> I didn't use ffio_ensure_seekback), because this apparently reallocates
> the buf
---
Follows reimar's suggestion for detecting UTF-16. If the detection goes
wrong, probing the format won't succeed, so this should not break
anything.
I didn't use ffio_ensure_seekback), because this apparently reallocates
the buffer - which we certainly don't want, because the probe API
doesn't
