[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compile issues
From: |
Daniel Pfeiffer |
Subject: |
Re: Compile issues |
Date: |
Sun, 4 Apr 2004 12:02:04 +0200 |
Saluton, Moin,
Stefan Monnier <address@hidden> skribis:
> >>> I do understand the i18n and compiler issues. Was that unclear?
> >> I can't remember what you're referring to.
> > Various of the patterns presumably won't work with internationalized
> > applications in locale fr_CH, for instance (I assume that `file'
> > becomes `fichier', for instance) and it doesn't look as though they
> > all work with non-ASCII commands and/or filenames. I also commented
> > on the classification and apparent redundancy of he patterns.
>
> Oh, I see now. Are these problems specific to the new compile.el or
> where they somehow absent in the old compile.el ?
These issues are not new, but nonetheless a huge headache. While creating
translated messages is something any translator can achieve, parsing them does
require regexp knowhow. The easy way out, (setq compilation-environment
'("LANG=C")), is hardly compatible with the goals of internationalization.
The present alist is a complex knowledge base, which covers so wide spread
message sources, that no one could possibly have access to them all, to try
them out. I myself have verified and completed maybe at most one third of
what is there. For the rest I just believed the old mode and its comments.
Even if I put in my knowledge of german and french, that would only be
guessing what the translation might really be. And it'd still cover only a
minuscule fraction of the possible languages.
> >> If you tell us what the user does,
> > Types C-c C-k and then C-x `.
Which is fixed, so how long are you going to discuss last weeks errors.
> > I doubt that helps.
>
> You bet. Looking at http://www.erlang.org/download/contrib/erlang.el (I
> assume that's what we're talking about), I don't see anything that would
> obviously break with the new code. But maybe the problem is that the new
> compile.el reads compilation-error-regexp-alist too early and doesn't
> notice when erlang.el adds stuff to it. Basically the problem is that in
> the old compile.el the variable was only read when you hit C-x ` or
> somesuch whereas in the new code it is read immediately when you turn on
> the compilation-mode.
This is true, but I believe it was Dave who said, he had a command that calls
compile. So it would be easy for erlang to modify the alist before that.
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
--
lerne / learn / apprends / läramå / ucz się Esperanto:
http://lernu.net/
- Re: Compile issues, Daniel Pfeiffer, 2004/04/01
- Re: Compile issues, Dave Love, 2004/04/01
- Re: Compile issues, monnier, 2004/04/01
- Re: Compile issues, Dave Love, 2004/04/02
- Re: Compile issues, Stefan Monnier, 2004/04/02
- Re: Compile issues, Dave Love, 2004/04/03
- Re: Compile issues, Stefan Monnier, 2004/04/03
- Re: Compile issues,
Daniel Pfeiffer <=
- Re: Compile issues, Stefan Monnier, 2004/04/04
- Re: Compile issues, Dave Love, 2004/04/05
- Re: Compile issues, Daniel Pfeiffer, 2004/04/06
- Re: Compile issues, Stefan Monnier, 2004/04/06
- Re: Compile issues, Daniel Pfeiffer, 2004/04/07
- Re: Compile issues, Dave Love, 2004/04/05
- Re: Compile issues, Stefan Monnier, 2004/04/05
- Re: Compile issues, Daniel Pfeiffer, 2004/04/06
- Compile issues fixed, Daniel Pfeiffer, 2004/04/07
- Re: Compile issues, Richard Stallman, 2004/04/04