[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [emms-help] Re: ogginfo problem
From: |
Jorgen Schaefer |
Subject: |
Re: [emms-help] Re: ogginfo problem |
Date: |
Tue, 18 Oct 2005 05:21:14 +0200 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) |
Yoni Rabkin <address@hidden> writes:
> On 10/16/05, Lucas Bonnet <address@hidden> wrote:
>> Jorgen Schaefer <address@hidden> writes:
>>
>> > Lucas Bonnet <address@hidden> writes:
>> >
>> >> Would it be possible to try to parse the info otherwise ? Or better, to
>> >> force a language environment when calling ogginfo ?
>> >
>> > (let ((process-environment (cons "LC_ALL=POSIX" process-environment)))
>> > ...)
>> >
>
> I think that this is a price of utilising the ubiquitous mp3info and
> ogginfo software. If the authors of mp3info or ogginfo change the
> output format we must adapt.
>
> If there is a different solution freely available I'd love to hear it.
The problem at hand is in the localization, which is a common
problem. UNIX utilizes output from programs a lot, and is very
format dependent. Localization is the most common problem there,
but it is easily solved by setting LC_ALL to POSIX, as I pointed
out above, which enforces the "standard" output format. This
should be done by all programs which parse other programs' output.
A "better" solution would be a library which provides a data
structure. Sadly, for UNIX (and Emacs!), a "data structure" is
often the output from a program.
Lisp machines, on the other hand.. ;-)
Greetings,
-- Jorgen
--
((email . "address@hidden") (www . "http://www.forcix.cx/")
(gpg . "1024D/028AF63C") (irc . "nick forcer on IRCnet"))