Re: libgettextpo: Ability to parse a string

[Bruno Haible]

Dwayne Bailey wrote:
> {I raised these on translation-i18n but am sending them here for more
> formal reporting.}

Thanks; you know I have been a bit inactive on translation-i18n in the last
few months.

> Currently you can only parse files read from stdin or from the file
> system.  Our code mostly pushes string representations of files around.
> It would be nice to have read and write methods that accept and output
> strings in addition to the file based functions.  Our current work
> around is to output to a temporary file, I haven't measured what kind of
> overhead this is causing.

Such read and write methods from/to memory buffers are implementable.

But I'm wondering: Why do you have the string representation of the file
in memory at all? Which operations are easier to perform with a long string
than with a po_file_t?

Bruno