From: bugbear on 25 May 2010 07:35 RedGrittyBrick wrote: > I would pay no attention to anybody who suggests that one of the worlds > largest industrial countries are only permitted to program in assembler > alleging that something like MOV AL, 61h is "sufficiently adapted to > [Chinese] culture". Even more amusingly the same individual is going to design a new programming language ;-) BugBear
From: Tom Anderson on 25 May 2010 08:20 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
From: Peter Olcott on 25 May 2010 10:24 "bugbear" <bugbear(a)trim_papermule.co.uk_trim> wrote in message news:z--dnXFWwKxpKGbWnZ2dnUVZ8oidnZ2d(a)brightview.co.uk... > RedGrittyBrick wrote: >> I would pay no attention to anybody who suggests that one >> of the worlds largest industrial countries are only >> permitted to program in assembler alleging that something >> like MOV AL, 61h is "sufficiently adapted to [Chinese] >> culture". > > Even more amusingly the same individual is going to design > a new programming > language ;-) > > BugBear It is already 75% implemented and is based on a subset of C++ / Java. The key missing aspect is exactly how far do I need to go when making this language available to an international market. It is an interpreted language that I estimate will be about 1/10 as fast as native code. It compiles its source code into its own virtual machine-code. Most of the design was of the virtual machine. I wanted to make it as easy to implement as possible, and simultaneously very fast.
From: Peter Olcott on 25 May 2010 10:29 "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.
From: Peter Olcott on 25 May 2010 10:32
"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. |