I'm not sure when this problem crept in because I have not printed
anything for a few days now.
I guess, however, it is related to changes I made in language.C

If I select anything besides english, I get ps errors telling me I have
not selected english. I added back the english entry in language.C,
which got rid of one warning saying that I did not have english defined.
I can print if I select english, but selecting canadian gives me error
boxes. So, I have to select canadian to spellcheck and then english to
print.

The reason I had deleted english from language.C is that Kevin's default
setup for aspell was pointing english to a small American dictionary.
Garst
Index: lyx-devel/ChangeLog
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.545
diff -u -u -r1.545 ChangeLog
--- lyx-devel/ChangeLog 2000/09/25 15:59:25     1.545
+++ lyx-devel/ChangeLog 2000/09/25 22:07:30
@@ -1,3 +1,6 @@
+2000-09-26  Garst Reese <[EMAIL PROTECTED]>
+       *src/language.C
+       *put back english with N_("American")
 2000-09-25  Juergen Vigna  <[EMAIL PROTECTED]>
 
        * src/frontends/kde/Dialogs.C (Dialogs): 
Index: lyx-devel/src/language.C
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/language.C,v
retrieving revision 1.14
diff -u -u -r1.14 language.C
--- lyx-devel/src/language.C    2000/09/25 11:10:14     1.14
+++ lyx-devel/src/language.C    2000/09/25 22:07:33
@@ -69,7 +69,7 @@
        { "danish", N_("Danish"), false, &iso8859_1, "da_DK" },
        { "default", N_("Document wide language"), false, &iso8859_1, "" },
        { "dutch", N_("Dutch"), false, &iso8859_1, "nl" },
-       // changed from en_EN (Garst)
+       { "english", N_("American"), false, &iso8859_1, "en" },
        { "esperanto", N_("Esperanto"), false, &iso8859_3, "eo" },
        // and what country code should esperanto have?? (Garst)
        { "estonian", N_("Estonian"), false, &iso8859_4, "et_EE" },

Reply via email to