Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Lars Gullik Bjønnes ...> writes:
>
> [...]
> > Send you attachments as application/octet-stream and be done with it.
>
> I am sorry, but this doesn't solve the problem. Indeed, when the attachment
> is encoded it may happen (as far as I know) th
Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
[...]
> Send you attachments as application/octet-stream and be done with it.
I am sorry, but this doesn't solve the problem. Indeed, when the attachment
is encoded it may happen (as far as I know) that a line starts with a dot.
So, if the mailer do
> This is absolutely not our bug.
I did not say this is lyx' fault. I said that lyx is vulnerable to an
existing mail system caveat, and lyx is likely to be the scapegoat. To
the best interest of lyx, I suggest that lyx do something with it.
You and other developers have all the reasons to say 't
Bo Peng <[EMAIL PROTECTED]> writes:
| > So a solution would be to change the format and replace "." by
| > something like \dot (like we do for \backspace). But then lyx2lyx
| > would have to be very very careful to avoid to replace \dot macros in
| > mathed, for example.
| >
| > Moreover, I am not
Bo Peng <[EMAIL PROTECTED]> writes:
| It sounds a bit unfair, but it is indeed lyx's responsibility to fix
| this problem, especially when we do not have control over mail
| servers/clients.
Way no!
This boils down to a user problem... sending as wrong attachment.
--
Lgb
Helge Hafting <[EMAIL PROTECTED]> writes:
| Already happened here - we use qmail. Now, I won't mind the next lyx
| being "nice" creating email-friendly
| files.
I would. Our format should not be restricted by any kind of
transmission format.
--
Lgb
"Jose' Matos" <[EMAIL PROTECTED]> writes:
| On Thursday 01 December 2005 14:15, Bo Peng wrote:
| >
| > 1. We fix this before 1.4.0 since otherwise a file format change can
| > only (?) happen for 1.5.0,
|
| Yes. I have reworked the file format and I don't want to make such a
change,
| not eve
Bo Peng <[EMAIL PROTECTED]> writes:
| Bug http://bugzilla.lyx.org/show_bug.cgi?id=2145 submitted.
This is not our bug.
--
Lgb
On Thu, Dec 01, 2005 at 07:53:34AM -0600, Bo Peng wrote:
> > IMO this is a bug in the mail programs Bo is using.
>
> This is a feature/bug of sendmail. Considering the dominance of this
> program, I would not say it is only "Bo's mail program".
>
> > The dot mechanism should
> > be completely tra
Bo Peng <[EMAIL PROTECTED]> writes:
>
> > Then for pities sake, take this to a sendmail forum. Fix the problem not
> > the symptoms.
>
> Have you read the previous posts? This is a known feature (written in
> the standards), not bug of sendmail.
That's correct. Having read some RFCs on the subje
On Sat, 3 Dec 2005 10:07:01 +0200, Martin Vermeer wrote:
> On Sat, Dec 03, 2005 at 01:23:38AM +0100, Enrico Forestieri wrote:
[...]
>> Alas, to my knowledge, XCmail is the only mailer with a GUI which lets me
>> open a mailbox in whatever place on disk or network it is located.
>> I hope that somed
> Then for pities sake, take this to a sendmail forum. Fix the problem not
> the symptoms.
Have you read the previous posts? This is a known feature (written in
the standards), not bug of sendmail.
> The point is: no one has ever complained about this problem here before
> in the 10 years of LyX'
Bo Peng wrote:
>> > > Take this to the developers of
>> > > XCMail or drop XCMail and use a mail client that works.
>
> I do not know other configurations and I never head of XCMail. What
> happened to me is that my .lyx files were changed by sendmail
Then for pities sake, take this to a sendmai
> > > Take this to the developers of
> > > XCMail or drop XCMail and use a mail client that works.
I do not know other configurations and I never head of XCMail. What
happened to me is that my .lyx files were changed by sendmail
(confirmed) and none of my recipients (using MS/OE, linux/mutt,
linux
On Saturday 03 December 2005 18:10, Bo Peng wrote:
> > Take this to the developers of
> > XCMail or drop XCMail and use a mail client that works.
>
> OE is also affected, if it is not causing the problem. How many lyx
> users will be left if you exclude OE users from them?
Almost all of 'em I'd ex
> Take this to the developers of
> XCMail or drop XCMail and use a mail client that works.
OE is also affected, if it is not causing the problem. How many lyx
users will be left if you exclude OE users from them?
Bo
Bo Peng wrote:
>> Several developers have told you that this isn't going to get fixed
>> before LyX 1.4 is released.
>
> I perfectly understand this.
>
>> They've explained why they think that a file format change would be a
>> bad idea at this stage.
>
> This is also fine, and I do understan
> Sendmail, TB and OE all seem innocent, as they would be given their user
> base. Or don't you think non-LyX-users would also sometimes want to send
> "dotty" files transparently?
My sendmail + OE combination has this problem. The user base of those
two are large, just that very few other files h
> Several developers have told you that this isn't going to get fixed before
> LyX 1.4 is released.
I perfectly understand this.
> They've explained why they think that a file format change would be a bad
> idea at this stage.
This is also fine, and I do understand the technical difficulties.
On Sat, Dec 03, 2005 at 05:26:23PM +, Angus Leeming wrote:
> Bo Peng wrote:
...
> > a) his trusty sendmail 50.2.3 that is sending a trillion email a day,
> > b) his MS/OE 10.0 that he paid $1000 for it, or
> > c) lyx 1.3.6 that opens an emailed .lyx file with problem.
> > You figure t
Bo Peng wrote:
>> This is _not_ a LyX problem, so it should not be fixed in LyX,
>> especially when the fix make the LyX code less straight-forward.
>
> I do not agree with you. Lyx is particularly vulnerable to this
> problem since every dot after an inset will be put as the first
> character of
> This is _not_ a LyX problem, so it should not be fixed in LyX,
> especially when the fix make the LyX code less straight-forward.
I do not agree with you. Lyx is particularly vulnerable to this
problem since every dot after an inset will be put as the first
character of a line. In my case, almos
On Fri, Dec 02, 2005 at 09:13:43AM +0100, Helge Hafting wrote:
> Jean-Marc Lasgouttes wrote:
>
> >So a solution would be to change the format and replace "." by
> >something like \dot (like we do for \backspace). But then lyx2lyx
> >would have to be very very careful to avoid to replace \dot macro
On Sat, Dec 03, 2005 at 01:23:38AM +0100, Enrico Forestieri wrote:
> On Fri, 2 Dec 2005 23:21:51 +0200, Martin Vermeer wrote:
> > On Fri, Dec 02, 2005 at 09:02:21PM +0100, Enrico Forestieri wrote:
>
> [...]
>
> > From the SMTP definition (RFC-822):
> >
> > "1. Before sending a line of mail text
On Fri, 2 Dec 2005 23:21:51 +0200, Martin Vermeer wrote:
> On Fri, Dec 02, 2005 at 09:02:21PM +0100, Enrico Forestieri wrote:
[...]
> From the SMTP definition (RFC-822):
>
> "1. Before sending a line of mail text the sender-SMTP checks
> the first character of the line. If it is a period, one
On Fri, Dec 02, 2005 at 09:02:21PM +0100, Enrico Forestieri wrote:
> Helge Hafting ha scritto:
>
> > Please submit bug reports - to the makers of bad email clients.
> > I tried sending with thunderbird 1.0.7 and receiving with mutt - no
> > problem.
>
> I tried to read some RFCs on the subject an
On Friday 02 December 2005 20:58, Bo Peng wrote:
>
> BTW, will the GUI improvements on compressed file handling
> (http://bugzilla.lyx.org/show_bug.cgi?id=2145) be done before 1.4.0?
Unlikely. We should concentrate in getting 1.4.0 out of the door. I think
that this is a feature that could in 1
> I tried to read some RFCs on the subject and I think that it could be
> the fault of broken email clients. I report here on some experiments I
> did.
You mean sendmail does not add a dot to your first single dot, rather
delete one from the line with double dots? This is different from what
I obs
Helge Hafting ha scritto:
> Please submit bug reports - to the makers of bad email clients.
> I tried sending with thunderbird 1.0.7 and receiving with mutt - no
> problem.
I tried to read some RFCs on the subject and I think that it could be
the fault of broken email clients. I report here on so
> "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes:
Helge> Jean-Marc Lasgouttes wrote:
>> So a solution would be to change the format and replace "." by
>> something like \dot (like we do for \backspace). But then lyx2lyx
>> would have to be very very careful to avoid to replace \dot macros
Jean-Marc Lasgouttes wrote:
So a solution would be to change the format and replace "." by
something like \dot (like we do for \backspace). But then lyx2lyx
would have to be very very careful to avoid to replace \dot macros in
mathed, for example.
Well, choose something unique so as to avoid
Bo Peng wrote:
Please submit bug reports - to the makers of bad email clients.
I tried sending with thunderbird 1.0.7 and receiving with mutt - no problem.
Mutt has this problem in my case. I guess this is because your
thunderbird encoded the file (in base64 I assume) before it pass the
m
On Thursday 01 December 2005 18:14, Jose' Matos wrote:
>
> Got it, my mistake. :-)
>
> I will fix it soon.
Done. I committed the fix. Two pieces of code where exchanged, my fault, I
took the chance to add better comments to code.
--
José Abílio
> 1. and 2. should work.> I can open a.lyx.gz with 1.4 if the file is in
> current format (245). It does
> not work with other formats, because lyx2lyx seems to have lost the ability
> to read gezipped files (at least with python 2.4).
Confirmed here. 1.4.0cvs can open, modify and save a gzipped
On Thursday 01 December 2005 17:50, Georg Baum wrote:
>
> 1. and 2. should work.
> I can open a.lyx.gz with 1.4 if the file is in current format (245). It
> does not work with other formats, because lyx2lyx seems to have lost the
> ability to read gezipped files (at least with python 2.4).
>
> José
Bo Peng wrote:
>> This is news to me. I've tried it and cannot get it to work either
>> with the GUI or command line. Maybe I'm just doing the wrong thing,
>> or maybe I need to make changes to the LyX/Mac package to make it
>> possible. Before I try the second, what is the proper procedure to
>>
> This is news to me. I've tried it and cannot get it to work either
> with the GUI or command line. Maybe I'm just doing the wrong thing,
> or maybe I need to make changes to the LyX/Mac package to make it
> possible. Before I try the second, what is the proper procedure to
> use LyX to open/save
On Dec 1, 2005, at 9:45 AM, Jose' Matos wrote:
Compress with gzip, lyx 1.4.0 reads and writes compressed files.
FWIW
lyx2lyx already does that, even in 1.3.x. We don't advertise this
as it is a
1.4.x feature but it already there. :-)
This is news to me. I've tried it and cannot get it to
On Thursday 01 December 2005 15:42, Georg Baum wrote:
> True, but in this case the risk of introducing lyx2lyx bugs is too high.
To me that is not the problem... really, lyx2lyx is easy. The problem is to
introduce bugs due to lyx parser, honestly. :-)
> Georg
--
José Abílio
> I think the situation right now is: if the file was compressed, it
> will stay so.
I guess I see what you meant: if a plain lyx file is opened, we should
have menu items 'save' and 'save gzipped'. If a gzipped file is
opened, we should have menu items 'save' and 'save plain/unzipped''.
This does
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> Compared to a configuration/GUI option, I think a menu item 'save
Bo> gziped' is easier to use and implement. In this way, user can open
Bo> plain/gziped lyx file and save either plain or gziped. For the
Bo> same file, I can 'save' to cvs/svn a
On 12/1/05, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> I think the situation right now is: if the file was compressed, it
> will stay so.
I am aware of this. Users will have to externally compress the lyx
file, and without a menu item, most users will not know this capacity.
Is build-in c
Bo Peng wrote:
>> IMO this is a bug in the mail programs Bo is using.
>
> This is a feature/bug of sendmail. Considering the dominance of this
> program, I would not say it is only "Bo's mail program".
Sorry, I did not follow the thread too closely, but have now reread it.
> I still do not get
> I would vote for a configureable option (with GUI too?).
> The good old text file is easier to handle when you want to
> CVS your .lyx files.
You are right. Even if I am using svn, which handles binary files
better than cvs, one can not diff a binary file. (But we will have
change-tracking syste
Bo Peng wrote:
Compress with gzip, lyx 1.4.0 reads and writes compressed files. FWIW
lyx2lyx already does that, even in 1.3.x. We don't advertise this as it is a
1.4.x feature but it already there. :-)
Then, problem solved, right? Is there a way to make compressed .lyx
default R/W format? Few
> Compress with gzip, lyx 1.4.0 reads and writes compressed files. FWIW
> lyx2lyx already does that, even in 1.3.x. We don't advertise this as it is a
> 1.4.x feature but it already there. :-)
Then, problem solved, right? Is there a way to make compressed .lyx
default R/W format? Few people will
On Thu, 1 Dec 2005, Bo Peng wrote:
> > Please submit bug reports - to the makers of bad email clients.
> > I tried sending with thunderbird 1.0.7 and receiving with mutt - no problem.
>
> Mutt has this problem in my case. I guess this is because your
> thunderbird encoded the file (in base64 I as
On Thursday 01 December 2005 14:25, Bo Peng wrote:
> > The workaround for users is simple - compress the file.
>
> First, we need to let *everyone* know this. Second, it is not
> convenient to compress and decompress a file.
As I have told before for 1.4.x you can work with the lyx file permanen
On Thursday 01 December 2005 14:15, Bo Peng wrote:
>
> 1. We fix this before 1.4.0 since otherwise a file format change can
> only (?) happen for 1.5.0,
Yes. I have reworked the file format and I don't want to make such a change,
not even paid. :-)
The format is more robust in 1.4.x but even
> Please submit bug reports - to the makers of bad email clients.
> I tried sending with thunderbird 1.0.7 and receiving with mutt - no problem.
Mutt has this problem in my case. I guess this is because your
thunderbird encoded the file (in base64 I assume) before it pass the
mail to sendmail, or
> So a solution would be to change the format and replace "." by
> something like \dot (like we do for \backspace). But then lyx2lyx
> would have to be very very careful to avoid to replace \dot macros in
> mathed, for example.
>
> Moreover, I am not sure that "." is the only bad case. In the
> exa
> IMO this is a bug in the mail programs Bo is using.
This is a feature/bug of sendmail. Considering the dominance of this
program, I would not say it is only "Bo's mail program".
> The dot mechanism should
> be completely transparent to the user. kmail has had this bug, too:
> http://bugs.kde.or
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> Blank and newline is (usually) not significant in latex, is it so
Bo> in lyx? If not, adding a blank after dot should fix the problem.
Unfortunately, blank is significant in the LyX format, and a newline
is not equivalent to a blank. The forma
Bo Peng wrote:
The moral of this story is
that it is not safe to send a lyx file in an email without zipping or
tarring it.
This is a serious problem! Since dot after *every inset* will be put
in a single line, this problem will be prominent for lyx, and lyx will
be blamed if this happens
Jean-Marc Lasgouttes wrote:
> We can probably works around it by a file format change, but such
> last-minutes changes carry a risk in themselves. Also, the problem
> with "From" becoming ">From" is similar, and solving this one is more
> complicated...
We can consider fixing this in the future,
>
> While I agree the problem you describe is annoying, it is not so
> terrible. In particular, it has been present at least since LyX 1.0...
I guess when lyx was not popular, there was no need to send lyx files
around. It is actually a good sign that I can now send lyx files,
instead of exported
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> I am not sure it should be critical, also I understand why you
>> chose that.
Bo> Yes, just imagine when you send an article in lyx format to your
Bo> adviser or an editor and get an email asking "Why do you put
Bo> double dots after all your c
> I am not sure it should be critical, also I understand why you chose
> that.
Yes, just imagine when you send an article in lyx format to your
adviser or an editor and get an email asking "Why do you put double
dots after all your citations?" (I did get an email like this.) . Even
worse, one may
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> Bug http://bugzilla.lyx.org/show_bug.cgi?id=2145 submitted. Bo
I am not sure it should be critical, also I understand why you chose
that.
JMarc
Bug http://bugzilla.lyx.org/show_bug.cgi?id=2145 submitted.
Bo
> The moral of this story is
> that it is not safe to send a lyx file in an email without zipping or
> tarring it.
This is a serious problem! Since dot after *every inset* will be put
in a single line, this problem will be prominent for lyx, and lyx will
be blamed if this happens to normal users.
Martin Vermeer ha scritto:
> From the sendmail man page:
>
> " With no flags, sendmail reads its standard input up to an end-of-file
>or a line consisting only of a single dot and sends a copy of the mes-
>sage found there to all of the addresses listed. It determines t
Jean-Marc Lasgouttes ha scritto:
>>"Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
>
> Enrico> I asked to a friend of mine to send me an email with lines
> Enrico> starting with a dot. Now I am using thunderbird to reply. Tell
> Enrico> me what you see. .this line starts with a si
On Wed, Nov 30, 2005 at 11:36:29AM +0100, Enrico Forestieri wrote:
> Bo Peng ha scritto:
> >>I asked to a friend of mine to send me an email with lines starting with
> >>a dot. Now I am using thunderbird to reply. Tell me what you see.
> >>.this line starts with a single dot
> >>..this line starts
Bo Peng ha scritto:
>>I asked to a friend of mine to send me an email with lines starting with
>>a dot. Now I am using thunderbird to reply. Tell me what you see.
>>.this line starts with a single dot
>>..this line starts with two and only two dots
>>this line ends with a single dot.
>>
>
>
> I s
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> I asked to a friend of mine to send me an email with lines
Enrico> starting with a dot. Now I am using thunderbird to reply. Tell
Enrico> me what you see. .this line starts with a single dot ..this
Enrico> line starts with two
> I asked to a friend of mine to send me an email with lines starting with
> a dot. Now I am using thunderbird to reply. Tell me what you see.
> .this line starts with a single dot
> ..this line starts with two and only two dots
> this line ends with a single dot.
>
I see correct things.
OE/thund
Bo Peng ha scritto:
>>I verified that MS/OE behaves the same, i.e., if the first character on
>>a line is a dot (no matter if in the email body or in a text attachment)
>>it gets doubled when sending. Conversely, if the first two characters on
>>a line are two dots they are collapsed to a single do
I am totally lost. The problem happens when
1. use windows/OE, send a windows-newlined file to gmail.com and my
unix mail server. Gmail.com get the file sent without change, unix
side gets a unix-newlined file with dots added.
2. use windows/ie/gmail.com, do the same thing, both gmail.com and
uni
> How do you verify this? I send an email with ./.. etc using MS/OE and
> get the correct email from another account.
More tests:
1. from windows -> windows, no problem.
2. from unix -> windows, no problem
3. from windows -> unix/ cc gmail.com, email/unix has dots, but not gmail.com
The only gues
> I verified that MS/OE behaves the same, i.e., if the first character on
> a line is a dot (no matter if in the email body or in a text attachment)
> it gets doubled when sending. Conversely, if the first two characters on
> a line are two dots they are collapsed to a single dot.
How do you verif
Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Bo Peng ...> writes:
> >
> > > Pay attention whether it is an email transfer problem. Dot doubling
> > > happens
> > > to me when the sender uses thunderbird.
> >
> > This is unlikely the case since
> > 1. I am using mutt and one of my friends
Bo Peng <[EMAIL PROTECTED]> writes:
>
> > Pay attention whether it is an email transfer problem. Dot doubling happens
> > to me when the sender uses thunderbird.
>
> This is unlikely the case since
> 1. I am using mutt and one of my friends will never use things like
> thunderbird (he is MS/OE on
> Pay attention whether it is an email transfer problem. Dot doubling happens
> to me when the sender uses thunderbird.
This is unlikely the case since
1. I am using mutt and one of my friends will never use things like
thunderbird (he is MS/OE only).
2. the files are sent via attachments
3. if th
Bo Peng <[EMAIL PROTECTED]> writes:
>
> Dear list,
>
> I have not been able to track down the source of this problem. Some of
> my colleagues use different versions of lyx (such as 1.3.5) on
> different platforms (linux/windows). If I send my lyx file
> (linux/1.3.6-1) to them and let them modif
Dear list,
I have not been able to track down the source of this problem. Some of
my colleagues use different versions of lyx (such as 1.3.5) on
different platforms (linux/windows). If I send my lyx file
(linux/1.3.6-1) to them and let them modify it, the revised version
will have additional dot (
76 matches
Mail list logo
