Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Sun, Oct 29, 2000 at 08:28:22AM +0100, Lars Gullik Bjønnes wrote:
| >
| > | 2) Another solution for 1) could be changing the
| > | language file, that comes with LyX. The first
| > | and second column in this file are ALWAYS the
| > | same. Why is that? We could use the second column
| > | for an equivalent language name, for example:
| >
| > Did you check the meanings of the fields?
|
| The second field is the babel name of the language, and it is not always
| equal to the first field (the LyX name).
|
| > I'd rather remove one of the fields instead of adding more.
| > (but then we would need a "babel" module.
|
| Why not add new fields to the languages file (ispell name, keymap name) ?
| The only drawback is decreasing the readability of this file.
And imposing addtional dependencies... it is ok for the ispell/babel
modules to depend on the language struct in LyX, but not ok for the
language struct to depend upon the ispell/babel module.
Lgb