Well, To track down this annoyance we need to know something of your system configuration at home.
List the following information: 1. Operating System 2. glibc library version and its locales listing. For example, myself: 1. Debian Unstable (2.6.5 kernel) 2. locales 2.3.2.ds1-1 3. glibc-2.3.2.ds1-12 How I modify the locales is with the package GkDebconf and under the base section select locales and choose which ones I want to be locally supported. Besides the standard Western I include the en_US.ISO-8859-1, en_US.ISO-8859-15 and en_US.UTF-8 locales to be generated for my Debian System. Of course you would choose the one's appropriate to your native language that is supported. But until one knows what your configuration is it's a "Shot in the Dark." -Marc On Tuesday 27 April 2004 11:23, John Coppens wrote: > On Tue, 27 Apr 2004 12:49:06 -0300 > > Beny Spira <[EMAIL PROTECTED]> wrote: > > > So, I understand that the document _did_ show correctly at your home, > > > but was modified when you sent it back to your work. Is that correct? > > > Or was it already missing characters when you worked on it at home? > > > > > > If you lost the characters while sending the document, how did you > > > send it? By FTP? If so, did you enable BINARY transmission? > > > > > > John > > > > Hi John > > The characters disappeared when the document was sent as an attachment > > by e-mail from home to work. There was no problem when the same document > > was sent before by e-mail from work to home. As Marc has already pointed > > out, it seems that there is a problem with the locales, but I do not > > know how to fix it. I do this kind of transfer (by e-mail) all the time > > with other files (.doc, .sxw, .txt etc...), and it never happened > > before. Any suggestions? > > Beny > > Which program do you use at work and which one at home to send the > documents? It's probably there that the problem lies. I think that the > easiest thing to do would be to ZIP the file before sending. I think the > mail program probably catalogs the .lyx extension as plain text or so, as > it may not be declared to be binary, and so all characters above 127 are > deleted. > > Also, be sure not to include it in the mail as a text attachment. Text is > not supposed to have accented characters. > > If you use an extension known to be binary, it should go through well. I > know there is a way to declare the .lyx extension as a binary mime, but I > don't know how... > > John > > PS: you could just rename it from xxx.lyx to xxx.zip. That might work too. > > PS2: I believe the mime types should be defined in your ~/.mailcap file or > /etc/mime.types, but I'm not sure which (I believe it's the latter - > /etc/mime.types) > > > -- > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > Beny Spira > > Departamento de Microbiologia > > Instituto de Ciências Biomédicas > > Universidade de São Paulo > > Av. Prof. Lineu Prestes 1374 > > São Paulo-SP CEP:05508-900 > > Tel: 5511-3091-7347 > > FAX: 5511-3091-7354 > > E-mail: [EMAIL PROTECTED] > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
