From: Peter Olcott on

"Lew" <noone(a)lewscanon.com> wrote in message
news:htgbuu$ma5$1(a)news.albasani.net...
> On 05/25/2010 01:35 AM, Peter Olcott wrote:
>> "Lew"<noone(a)lewscanon.com> wrote in message
>> news:htfial$g79$1(a)news.albasani.net...
>>> Peter Olcott wrote:
>>>>>
>>>>> --
>>>>> Lew
>>>
>>> Please don't quote sigs.
>>>
>>> --
>>> Lew
>>> Please don't quote sigs.
>>
>> I make it a rule to never follow rules, I only follow the
>> reasons behind the rules if there are any. Because of
>> this
>> what you said makes no sense. I might as well ask you to
>> ALWAYS make sure to quote sigs. What difference does it
>> make?
>
> Plonk.
>
> --
> Lew

My actual rule on this is to make sure to always quote
everything to maintain the complete context of the
conversation until this context becomes irrelevant to the
current discussion. When the context becomes irrelevant,
then trim the irrelevant parts. This most often gets to
about fiver levels deep.

I do recall someone explicitly asking me to always quote at
least the identifier part of the message so that they could
find the messages that they needed to reply to.


From: Lars Enderin on
On 2010-05-25 16:32, Peter Olcott wrote:
> "Lew" <noone(a)lewscanon.com> wrote in message
> news:htgbuu$ma5$1(a)news.albasani.net...
>> On 05/25/2010 01:35 AM, Peter Olcott wrote:
>>> "Lew"<noone(a)lewscanon.com> wrote in message
>>> news:htfial$g79$1(a)news.albasani.net...
>>>> Peter Olcott wrote:
>>>>>>
>>>>>> --
>>>>>> Lew
>>>>
>>>> Please don't quote sigs.
>>>>
>>>> --
>>>> Lew
>>>> Please don't quote sigs.
>>>
>>> I make it a rule to never follow rules, I only follow the
>>> reasons behind the rules if there are any. Because of
>>> this
>>> what you said makes no sense. I might as well ask you to
>>> ALWAYS make sure to quote sigs. What difference does it
>>> make?
>>
>> Plonk.
>>
>> --
>> Lew
>
> So no reason then besides your own personal idiosyncrasy.

Not true. It's a general recommendation that you should not quote sigs.
Decent newsreaders, like Thunderbird, will (automatically) not cite
correctly delimited signatures when you compose a reply. The correct
delimiter is a line with only the three characters "-- " (two dashes and
a space).


From: Peter Olcott on

"Lars Enderin" <lars.enderin(a)telia.com> wrote in message
news:4BFBE7D8.1010900(a)telia.com...
> On 2010-05-25 16:32, Peter Olcott wrote:
>> "Lew" <noone(a)lewscanon.com> wrote in message
>> news:htgbuu$ma5$1(a)news.albasani.net...
>>> On 05/25/2010 01:35 AM, Peter Olcott wrote:
>>>> "Lew"<noone(a)lewscanon.com> wrote in message
>>>> news:htfial$g79$1(a)news.albasani.net...
>>>>> Peter Olcott wrote:
>>>>>>>
>>>>>>> --
>>>>>>> Lew
>>>>>
>>>>> Please don't quote sigs.
>>>>>
>>>>> --
>>>>> Lew
>>>>> Please don't quote sigs.
>>>>
>>>> I make it a rule to never follow rules, I only follow
>>>> the
>>>> reasons behind the rules if there are any. Because of
>>>> this
>>>> what you said makes no sense. I might as well ask you
>>>> to
>>>> ALWAYS make sure to quote sigs. What difference does it
>>>> make?
>>>
>>> Plonk.
>>>
>>> --
>>> Lew
>>
>> So no reason then besides your own personal idiosyncrasy.
>
> Not true. It's a general recommendation that you should
> not quote sigs.
> Decent newsreaders, like Thunderbird, will (automatically)
> not cite
> correctly delimited signatures when you compose a reply.
> The correct
> delimiter is a line with only the three characters "-- "
> (two dashes and
> a space).
>
>
OK then I will switch to Thunderbird. Peolpe in other groups
kept bugging me about other issues they were having with my
Outlook Express so I finally switched. The only thing that
Outlook express does better than Thunderbird is the "Watch"
feature.


From: Patricia Shanahan on
Peter Olcott wrote:
> "Tom Anderson" <twic(a)urchin.earth.li> wrote in message
> news:alpine.DEB.1.10.1005251308010.11939(a)urchin.earth.li...
>> On Mon, 24 May 2010, Mike Schilling wrote:
>>
>>> Patricia Shanahan wrote:
>>>> Peter Olcott wrote:
>>>> ...
>>>>> I just want to know if it makes any sense to convert
>>>>> local
>>>>> punctuation and local digits to ASCII for the computer
>>>>> language that I am designing. That is the sole purpose
>>>>> of
>>>>> this thread. I used Chinese Java to provide a
>>>>> completely
>>>>> concrete example.
>>>> ...
>>>>
>>>> I don't have any experience with Chinese Java, but I
>>>> have read a
>>>> couple of French Fortran programs, and France really
>>>> does have
>>>> language purity laws. The identifiers and comments were
>>>> all in
>>>> French, but the punctuation in the actual code was
>>>> normal Fortran
>>>> punctuation. In particular, real constants were written
>>>> as e.g.
>>>> "3.14", not "3,14" as one would expect in French.
>>> Using the French decimal point would necessitate other
>>> changes, since
>>> otherwise
>>>
>>> CALL FOO(3,14)
>>>
>>> would be ambiguous in whether it calls FOO with two
>>> integers or a real, of
>>> course.
>> On a related note, SAP R/3 is German, and uses German
>> number formats, with commas, in some of its low-level
>> interfaces. The system i'm working on gets some feeds of
>> data which originate in SAP, and so it contains parsing
>> routines which are specifically for German numbers.
>>
>> It also uses German text in some places - the example that
>> springs to mind is codes used to identify the roles of
>> parties to a transaction. The fun thing is that these are
>> localised in the UI, but not in the low-level interfaces,
>> so as far as the SAP operators i work with are concerned,
>> if someone is a ship-to party (ie customer!) then their
>> code is SH, but when i talk to SAP directly, it's WE. WE
>> is presumably short for some German word that means
>> 'ship-to party', but i'm afraid i couldn't tell you what.
>>
>> On another related note, i understand that in German CSV
>> files, the comma is a semicolon, presumably because the
>> decimal point is a comma.
>>
>> I further understand that this piece of software:
>>
>> http://www.hybris.com/hybris/en/Products/suite.html
>>
>> Is made in Germany, and has a CSV file import interface
>> which only supports semicolonic CSV files. I understand
>> that this leads to fun times when trying to use it in a
>> system running in a non-German locale, since you have to
>> bodge in a CSV translation layer somewhere in your data
>> flow. I should add that this information is second-hand
>> and somewhat out of date, so this may have been fixed.
>>
>> I should also add that i'm not specifically ragging on the
>> Germans here, who i am sure are stout fellows to a man,
>> it's just that those happen to be the examples i'm aware
>> of.
>>
>> tom
>>
>> --
>> Vive la chimie, en particulier, et la connaissance en
>> general. --
>> Herve This
>
> So some computer languages (I am guessing that SAP could be
> construed as a computer language) do use local punctuation.
>
>

It depends what you mean by "local". If a program is developed in
Germany using German punctuation, for that program "," as decimal
separator is normal. An option for using "." instead would be a
case of using local punctuation.

The key issue you need to face is whether you can get away with one set
of punctuation, or need to localize the punctuation.

Patricia
From: Peter Olcott on

"Patricia Shanahan" <pats(a)acm.org> wrote in message
news:qe-dnXQSKdYNcWbWnZ2dnUVZ_uOdnZ2d(a)earthlink.com...
> Peter Olcott wrote:
>> "Tom Anderson" <twic(a)urchin.earth.li> wrote in message
>> news:alpine.DEB.1.10.1005251308010.11939(a)urchin.earth.li...
>>> On Mon, 24 May 2010, Mike Schilling wrote:
>>>

>> So some computer languages (I am guessing that SAP could
>> be construed as a computer language) do use local
>> punctuation.
>
> It depends what you mean by "local". If a program is
> developed in
> Germany using German punctuation, for that program "," as
> decimal
> separator is normal. An option for using "." instead would
> be a
> case of using local punctuation.
>
> The key issue you need to face is whether you can get away
> with one set
> of punctuation, or need to localize the punctuation.
>
> Patricia

The specific case in point on another thread on another
newsgroup was that it was proposed that the local Comma be
used to delimit parameters in a function call.

My view on this is that the ASCII Comma would not be
understood from the English language context and thus need
to be localized but instead would be understood as the
Java/C++ (native language) parameter delimiter.