[Pharo-project] OSProcess ... ported to 2.0?
As I take yet another stab at getting the Metacello Preview running on Pharo2.0, I find that OSProcess is sprinkled with references to FileDirectory ... at least in the packages referenced by the configuration, so I'm wondering if a port exists for Phar0-2.0 ... At the moment OSProcess is a prerequisite .... If there is an alternate mechanism for running shell commands from Pharo2.0, then I assume that I'll be able to use that instead ... Dale
On 2012-09-25, at 01:11, Dale Henrichs <dhenrich@vmware.com> wrote:
As I take yet another stab at getting the Metacello Preview running on Pharo2.0, I find that OSProcess is sprinkled with references to FileDirectory ... at least in the packages referenced by the configuration, so I'm wondering if a port exists for Phar0-2.0 ... At the moment OSProcess is a prerequisite ....
use my compatibility layer for FileDirectory, which wraps around FileReference: http://smalltalkhub.com/mc/dh83/fisleg/main With that it should be possible to load most old code in 2.0. There are a 4 methods or so I haven't ported yet and I should properly isolate the package...
If there is an alternate mechanism for running shell commands from Pharo2.0, then I assume that I'll be able to use that instead ...
currently there isn't any other option :/
Thanks Cami... Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Monday, September 24, 2012 11:23:35 PM | Subject: Re: [Pharo-project] OSProcess ... ported to 2.0? | | | On 2012-09-25, at 01:11, Dale Henrichs <dhenrich@vmware.com> wrote: | | > As I take yet another stab at getting the Metacello Preview running | > on Pharo2.0, I find that OSProcess is sprinkled with references to | > FileDirectory ... at least in the packages referenced by the | > configuration, so I'm wondering if a port exists for Phar0-2.0 ... | > At the moment OSProcess is a prerequisite .... | | use my compatibility layer for FileDirectory, which wraps around | FileReference: | http://smalltalkhub.com/mc/dh83/fisleg/main | | With that it should be possible to load most old code in 2.0. | There are a 4 methods or so I haven't ported yet and I should | properly isolate the package... | | > If there is an alternate mechanism for running shell commands from | > Pharo2.0, then I assume that I'll be able to use that instead ... | | currently there isn't any other option :/ |
Cami, Your code seems to have conflicts with the implementation of FileSystem in Pharo-2.0 ... besides overriding a number of methods (most that I looked at involved comments) there are a couple of places where the class names have been changed ... so it looks like your wrapper code has become outdated ... Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Monday, September 24, 2012 11:23:35 PM | Subject: Re: [Pharo-project] OSProcess ... ported to 2.0? | | | On 2012-09-25, at 01:11, Dale Henrichs <dhenrich@vmware.com> wrote: | | > As I take yet another stab at getting the Metacello Preview running | > on Pharo2.0, I find that OSProcess is sprinkled with references to | > FileDirectory ... at least in the packages referenced by the | > configuration, so I'm wondering if a port exists for Phar0-2.0 ... | > At the moment OSProcess is a prerequisite .... | | use my compatibility layer for FileDirectory, which wraps around | FileReference: | http://smalltalkhub.com/mc/dh83/fisleg/main | | With that it should be possible to load most old code in 2.0. | There are a 4 methods or so I haven't ported yet and I should | properly isolate the package... | | > If there is an alternate mechanism for running shell commands from | > Pharo2.0, then I assume that I'll be able to use that instead ... | | currently there isn't any other option :/ |
On 2012-09-25, at 18:59, Dale Henrichs <dhenrich@vmware.com> wrote:
Cami,
Your code seems to have conflicts with the implementation of FileSystem in Pharo-2.0 ... besides overriding a number of methods (most that I looked at involved comments) there are a couple of places where the class names have been changed ... so it looks like your wrapper code has become outdated ...
Dale
ok, that's what I feared :/ since I did only a quick tryout and didn't properly separate the classes from the rest of the FileSystem I opened an issue on the tracker, currently I have to take a break from fixing stuff and work on my phd :P... https://code.google.com/p/pharo/issues/detail?id=6740 cami
Cami, Work on Phd? Do you have a bug number for that? Thanks for the effort, man! I'll just wait a bit longer before integration:) Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, September 26, 2012 2:10:36 AM | Subject: Re: [Pharo-project] OSProcess ... ported to 2.0? | | | On 2012-09-25, at 18:59, Dale Henrichs <dhenrich@vmware.com> wrote: | | > Cami, | > | > Your code seems to have conflicts with the implementation of | > FileSystem in Pharo-2.0 ... besides overriding a number of methods | > (most that I looked at involved comments) there are a couple of | > places where the class names have been changed ... so it looks | > like your wrapper code has become outdated ... | > | > Dale | | ok, that's what I feared :/ since I did only a quick tryout and | didn't properly separate the | classes from the rest of the FileSystem | | I opened an issue on the tracker, currently I have to take a break | from fixing stuff and work | on my phd :P... | | https://code.google.com/p/pharo/issues/detail?id=6740 | | cami |
Hello everyone, While looking at bug 6596, I started wondering why we didn't have more options to print dates (and/or their parts). I've gathered "date formats" printing options from various sources and started implementing all those different formats and options. I have implemented 6 new methods to print the different date components/parts/timespans. Do you think this stuff would be useful? Anything missing?  Here are the supported format options I came up with. Most of them are already implemented, now it's just a matter of writing the numerous missing unit tests! ;) Comments, complaints and suggestions are welcome! a) Year formats (#printYearWithFormat:) May 14, -7 May 14 2002 1-Year, signed (-7 and 2002) 2-Year, last 2 digits, signed (-07 and 02) 3-Year, last 3 digits, signed (-007 and 002) 4-Year, last 4 digits or more digits if year is greater than 9999, signed (-0007 and 2002) 5-Year, unsigned (7 and 2002) 6-Year, last 2 digits, unsigned (07 and 02) 7-Year, last 3 digits, unsigned (007 and 002) 8-Year, last 4 digits or more digits if year is greater than 9999, unsigned (0007 and 2002) 9-Year in roman numerals (n/a and MMII) 10-Year (full, no padding) with epoch AD/BC (7 BC and 2002 AD) 11-Year (full, no padding) with epoch A.D./B.C. (7 B.C. and 2002 A.D.) 12-Year (full, no padding) with epoch ad/bc (7 bc and 2002 ad) 13-Year (full, no padding) with epoch a.d./b.c. (7 b.c. and 2002 a.d.) b) Month formats (#printMonthWithFormat:) Tuesday, September 18 2012 1-Month , no padding (9) 2-Month padded to 2 digits (09) 3-Month name abreviation (Sep) 4-Month name (September) 5-Month name abreviation in uppercase (SEP) 6-Month name in uppercase (SEPTEMBER) 7-Month name abreviation in lowercase (sep) 8-Month name in lowercase (september) 9-Month number in Roman numerals (IX) c) Day formats (#printDayWithFormat:) Saturday, December 1 2012    1-Day of the month, no padding (1) 2-Day of the month padded to 2 digits (01) 3-Abbreviated day of week (Sat) 4-Complete day of week (Saturday) 5-Abbreviated day of week in uppercase (SAT) 6-Complete day of week in uppercase (SATURDAY) 7-Abbreviated day of week in lowercase (sat) 8-Complete day of week lowercase (saturday) 9-Day of the month with english suffix (1st) 10-Day of the year (336) 11-Day of the year with English suffix (336th) 12-Day of the week index [0=sunday 6 = saturday] (6) 13-Day of the week index [1=sunday 7 = saturday] (7) 14-Day of the week index [0=monday 6 = sunday] (5) 15-Day of the week index [1=monday 7 = sunday] (6) 16-Julian day, i.e. days since January 1, 4712 BC (2456263) d) Week formats (#printWeekWithFormat:) 1-Week of the year (1..53) where Sunday if the first day of the week 2-Week of the year (1..53) where Monday if the first day of the week e) Era formats (#printEraWithFormat:) 1-Era AD or BC 2-Era A.D. or B.C. 3-Era ad or bc 4-Era a.d. or b.c. f) Century formats (#printCenturyWithFormat:) 1-Century (20) 2-Century with English suffix (20th)  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
On Oct 28, 2012, at 11:08 AM, Benoit St-Jean wrote:
Hello everyone,
While looking at bug 6596, I started wondering why we didn't have more options to print dates (and/or their parts). I've gathered "date formats" printing options from various sources and started implementing all those different formats and options. I have implemented 6 new methods to print the different date components/parts/timespans.
Do you think this stuff would be useful?
Yes I often just want the one that is not there :) Note that in French we have
14 mai 2002
So it would be good to support it. I imagine that we can with the #(d m y) description.
Anything missing?
Here are the supported format options I came up with. Most of them are already implemented, now it's just a matter of writing the numerous missing unit tests! ;)
Comments, complaints and suggestions are welcome!
a) Year formats (#printYearWithFormat:)
May 14, -7 May 14 2002
1-Year, signed (-7 and 2002) 2-Year, last 2 digits, signed (-07 and 02) 3-Year, last 3 digits, signed (-007 and 002) 4-Year, last 4 digits or more digits if year is greater than 9999, signed (-0007 and 2002) 5-Year, unsigned (7 and 2002) 6-Year, last 2 digits, unsigned (07 and 02) 7-Year, last 3 digits, unsigned (007 and 002) 8-Year, last 4 digits or more digits if year is greater than 9999, unsigned (0007 and 2002) 9-Year in roman numerals (n/a and MMII) 10-Year (full, no padding) with epoch AD/BC (7 BC and 2002 AD) 11-Year (full, no padding) with epoch A.D./B.C. (7 B.C. and 2002 A.D.) 12-Year (full, no padding) with epoch ad/bc (7 bc and 2002 ad) 13-Year (full, no padding) with epoch a.d./b.c. (7 b.c. and 2002 a.d.)
b) Month formats (#printMonthWithFormat:)
Tuesday, September 18 2012
1-Month , no padding (9) 2-Month padded to 2 digits (09) 3-Month name abreviation (Sep) 4-Month name (September) 5-Month name abreviation in uppercase (SEP) 6-Month name in uppercase (SEPTEMBER) 7-Month name abreviation in lowercase (sep) 8-Month name in lowercase (september) 9-Month number in Roman numerals (IX)
c) Day formats (#printDayWithFormat:)
Saturday, December 1 2012
1-Day of the month, no padding (1) 2-Day of the month padded to 2 digits (01) 3-Abbreviated day of week (Sat) 4-Complete day of week (Saturday) 5-Abbreviated day of week in uppercase (SAT) 6-Complete day of week in uppercase (SATURDAY) 7-Abbreviated day of week in lowercase (sat) 8-Complete day of week lowercase (saturday) 9-Day of the month with english suffix (1st) 10-Day of the year (336) 11-Day of the year with English suffix (336th) 12-Day of the week index [0=sunday 6 = saturday] (6) 13-Day of the week index [1=sunday 7 = saturday] (7) 14-Day of the week index [0=monday 6 = sunday] (5) 15-Day of the week index [1=monday 7 = sunday] (6) 16-Julian day, i.e. days since January 1, 4712 BC (2456263)
d) Week formats (#printWeekWithFormat:)
1-Week of the year (1..53) where Sunday if the first day of the week 2-Week of the year (1..53) where Monday if the first day of the week
e) Era formats (#printEraWithFormat:)
1-Era AD or BC 2-Era A.D. or B.C. 3-Era ad or bc 4-Era a.d. or b.c.
f) Century formats (#printCenturyWithFormat:)
1-Century (20) 2-Century with English suffix (20th)
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Yeah, same thing here... But I was wondering about other languages... I mean, yes we can support French and English but what about Spanish, Italian, etc? Should we use the NaturalLanguageTranslator tool/mechanism ?  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
________________________________ From: Stéphane Ducasse <stephane.ducasse@inria.fr> To: Pharo-project@lists.gforge.inria.fr; Benoit St-Jean <bstjean@yahoo.com> Sent: Sunday, October 28, 2012 12:56:24 PM Subject: Re: [Pharo-project] Bug 6596
On Oct 28, 2012, at 11:08 AM, Benoit St-Jean wrote:
Hello everyone,
While looking at bug 6596, I started wondering why we didn't have more options to print dates (and/or their parts). I've gathered "date formats" printing options from various sources and started implementing all those different formats and options. I have implemented 6 new methods to print the different date components/parts/timespans.
Do you think this stuff would be useful?Â
Yes I often just want the one that is not there :) Note that in French we have
 14 mai 2002
So it would be good to support it. I imagine that we can with the #(d m y) description.
Anything missing?Â
Here are the supported format options I came up with. Most of them are already implemented, now it's just a matter of writing the numerous missing unit tests! ;)
Comments, complaints and suggestions are welcome!
a) Year formats (#printYearWithFormat:)
May 14, -7 May 14 2002
1-Year, signed (-7 and 2002) 2-Year, last 2 digits, signed (-07 and 02) 3-Year, last 3 digits, signed (-007 and 002) 4-Year, last 4 digits or more digits if year is greater than 9999, signed (-0007 and 2002) 5-Year, unsigned (7 and 2002) 6-Year, last 2 digits, unsigned (07 and 02) 7-Year, last 3 digits, unsigned (007 and 002) 8-Year, last 4 digits or more digits if year is greater than 9999, unsigned (0007 and 2002) 9-Year in roman numerals (n/a and MMII) 10-Year (full, no padding) with epoch AD/BC (7 BC and 2002 AD) 11-Year (full, no padding) with epoch A.D./B.C. (7 B.C. and 2002 A.D.) 12-Year (full, no padding) with epoch ad/bc (7 bc and 2002 ad) 13-Year (full, no padding) with epoch a.d./b.c. (7 b.c. and 2002 a.d.)
b) Month formats (#printMonthWithFormat:)
Tuesday, September 18 2012
1-Month , no padding (9) 2-Month padded to 2 digits (09) 3-Month name abreviation (Sep) 4-Month name (September) 5-Month name abreviation in uppercase (SEP) 6-Month name in uppercase (SEPTEMBER) 7-Month name abreviation in lowercase (sep) 8-Month name in lowercase (september) 9-Month number in Roman numerals (IX)
c) Day formats (#printDayWithFormat:)
Saturday, December 1 2012 Â Â 1-Day of the month, no padding (1) 2-Day of the month padded to 2 digits (01) 3-Abbreviated day of week (Sat) 4-Complete day of week (Saturday) 5-Abbreviated day of week in uppercase (SAT) 6-Complete day of week in uppercase (SATURDAY) 7-Abbreviated day of week in lowercase (sat) 8-Complete day of week lowercase (saturday) 9-Day of the month with english suffix (1st) 10-Day of the year (336) 11-Day of the year with English suffix (336th) 12-Day of the week index [0=sunday 6 = saturday] (6) 13-Day of the week index [1=sunday 7 = saturday] (7) 14-Day of the week index [0=monday 6 = sunday] (5) 15-Day of the week index [1=monday 7 = sunday] (6) 16-Julian day, i.e. days since January 1, 4712 BC (2456263)
d) Week formats (#printWeekWithFormat:)
1-Week of the year (1..53) where Sunday if the first day of the week 2-Week of the year (1..53) where Monday if the first day of the week
e) Era formats (#printEraWithFormat:)
1-Era AD or BC 2-Era A.D. or B.C. 3-Era ad or bc 4-Era a.d. or b.c.
f) Century formats (#printCenturyWithFormat:)
1-Century (20) 2-Century with English suffix (20th)
 ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
I started a (STAMP)[https://github.com/jeremyw/stamp] port for Pharo http://smalltalkhub.com/mc/dh83/c/main which follows an example drive date-formatting scheme. Instead of using a cryptic compressed form you use an example string DateAndTime now stompFormat: '2012-12-31 14:32:12'. DateAndTime now stompFormat: '2012/31/12 14:32:12'. best cami On 2012-10-28, at 17:56, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Oct 28, 2012, at 11:08 AM, Benoit St-Jean wrote:
Hello everyone,
While looking at bug 6596, I started wondering why we didn't have more options to print dates (and/or their parts). I've gathered "date formats" printing options from various sources and started implementing all those different formats and options. I have implemented 6 new methods to print the different date components/parts/timespans.
Do you think this stuff would be useful?
Yes I often just want the one that is not there :) Note that in French we have
14 mai 2002
So it would be good to support it. I imagine that we can with the #(d m y) description.
Anything missing?
Here are the supported format options I came up with. Most of them are already implemented, now it's just a matter of writing the numerous missing unit tests! ;)
Comments, complaints and suggestions are welcome!
a) Year formats (#printYearWithFormat:)
May 14, -7 May 14 2002
1-Year, signed (-7 and 2002) 2-Year, last 2 digits, signed (-07 and 02) 3-Year, last 3 digits, signed (-007 and 002) 4-Year, last 4 digits or more digits if year is greater than 9999, signed (-0007 and 2002) 5-Year, unsigned (7 and 2002) 6-Year, last 2 digits, unsigned (07 and 02) 7-Year, last 3 digits, unsigned (007 and 002) 8-Year, last 4 digits or more digits if year is greater than 9999, unsigned (0007 and 2002) 9-Year in roman numerals (n/a and MMII) 10-Year (full, no padding) with epoch AD/BC (7 BC and 2002 AD) 11-Year (full, no padding) with epoch A.D./B.C. (7 B.C. and 2002 A.D.) 12-Year (full, no padding) with epoch ad/bc (7 bc and 2002 ad) 13-Year (full, no padding) with epoch a.d./b.c. (7 b.c. and 2002 a.d.)
b) Month formats (#printMonthWithFormat:)
Tuesday, September 18 2012
1-Month , no padding (9) 2-Month padded to 2 digits (09) 3-Month name abreviation (Sep) 4-Month name (September) 5-Month name abreviation in uppercase (SEP) 6-Month name in uppercase (SEPTEMBER) 7-Month name abreviation in lowercase (sep) 8-Month name in lowercase (september) 9-Month number in Roman numerals (IX)
c) Day formats (#printDayWithFormat:)
Saturday, December 1 2012
1-Day of the month, no padding (1) 2-Day of the month padded to 2 digits (01) 3-Abbreviated day of week (Sat) 4-Complete day of week (Saturday) 5-Abbreviated day of week in uppercase (SAT) 6-Complete day of week in uppercase (SATURDAY) 7-Abbreviated day of week in lowercase (sat) 8-Complete day of week lowercase (saturday) 9-Day of the month with english suffix (1st) 10-Day of the year (336) 11-Day of the year with English suffix (336th) 12-Day of the week index [0=sunday 6 = saturday] (6) 13-Day of the week index [1=sunday 7 = saturday] (7) 14-Day of the week index [0=monday 6 = sunday] (5) 15-Day of the week index [1=monday 7 = sunday] (6) 16-Julian day, i.e. days since January 1, 4712 BC (2456263)
d) Week formats (#printWeekWithFormat:)
1-Week of the year (1..53) where Sunday if the first day of the week 2-Week of the year (1..53) where Monday if the first day of the week
e) Era formats (#printEraWithFormat:)
1-Era AD or BC 2-Era A.D. or B.C. 3-Era ad or bc 4-Era a.d. or b.c.
f) Century formats (#printCenturyWithFormat:)
1-Century (20) 2-Century with English suffix (20th)
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Hello 2012/10/28 Camillo Bruni <camillobruni@gmail.com>
I started a (STAMP)[https://github.com/jeremyw/stamp] port for Pharo
http://smalltalkhub.com/mc/dh83/c/main
which follows an example drive date-formatting scheme. Instead of using a cryptic compressed form you use an example string
DateAndTime now stompFormat: '2012-12-31 14:32:12'. DateAndTime now stompFormat: '2012/31/12 14:32:12'.
I like it
On 28 Oct 2012, at 18:07, Camillo Bruni <camillobruni@gmail.com> wrote:
I started a (STAMP)[https://github.com/jeremyw/stamp] port for Pharo
http://smalltalkhub.com/mc/dh83/c/main
which follows an example drive date-formatting scheme. Instead of using a cryptic compressed form you use an example string
DateAndTime now stompFormat: '2012-12-31 14:32:12'. DateAndTime now stompFormat: '2012/31/12 14:32:12'.
I was planning on doing the same thing, based on the way Go does it ⦠You write too much code !
On 2012-10-28, at 18:38, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 28 Oct 2012, at 18:07, Camillo Bruni <camillobruni@gmail.com> wrote:
I started a (STAMP)[https://github.com/jeremyw/stamp] port for Pharo
http://smalltalkhub.com/mc/dh83/c/main
which follows an example drive date-formatting scheme. Instead of using a cryptic compressed form you use an example string
DateAndTime now stompFormat: '2012-12-31 14:32:12'. DateAndTime now stompFormat: '2012/31/12 14:32:12'.
I was planning on doing the same thing, based on the way Go does it â¦
You write too much code !
it's far from finished :P, so stop complaining :D
Unfortunately Stéphane, it looks like someone put the axe in all the Localization/Translation stuff... Unless there's a new Locale/Translation framework and I missed it, it'll take some major effort to be able to print months, week days and other stuff in French or any other language! :( Right now, the localization/translation code is broken in Pharo.  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
________________________________ From: Stéphane Ducasse <stephane.ducasse@inria.fr> To: Pharo-project@lists.gforge.inria.fr; Benoit St-Jean <bstjean@yahoo.com> Sent: Sunday, October 28, 2012 12:56:24 PM Subject: Re: [Pharo-project] Bug 6596
On Oct 28, 2012, at 11:08 AM, Benoit St-Jean wrote:
Hello everyone,
While looking at bug 6596, I started wondering why we didn't have more options to print dates (and/or their parts). I've gathered "date formats" printing options from various sources and started implementing all those different formats and options. I have implemented 6 new methods to print the different date components/parts/timespans.
Do you think this stuff would be useful?Â
Yes I often just want the one that is not there :) Note that in French we have
 14 mai 2002
So it would be good to support it. I imagine that we can with the #(d m y) description.
Anything missing?Â
Here are the supported format options I came up with. Most of them are already implemented, now it's just a matter of writing the numerous missing unit tests! ;)
Comments, complaints and suggestions are welcome!
a) Year formats (#printYearWithFormat:)
May 14, -7 May 14 2002
1-Year, signed (-7 and 2002) 2-Year, last 2 digits, signed (-07 and 02) 3-Year, last 3 digits, signed (-007 and 002) 4-Year, last 4 digits or more digits if year is greater than 9999, signed (-0007 and 2002) 5-Year, unsigned (7 and 2002) 6-Year, last 2 digits, unsigned (07 and 02) 7-Year, last 3 digits, unsigned (007 and 002) 8-Year, last 4 digits or more digits if year is greater than 9999, unsigned (0007 and 2002) 9-Year in roman numerals (n/a and MMII) 10-Year (full, no padding) with epoch AD/BC (7 BC and 2002 AD) 11-Year (full, no padding) with epoch A.D./B.C. (7 B.C. and 2002 A.D.) 12-Year (full, no padding) with epoch ad/bc (7 bc and 2002 ad) 13-Year (full, no padding) with epoch a.d./b.c. (7 b.c. and 2002 a.d.)
b) Month formats (#printMonthWithFormat:)
Tuesday, September 18 2012
1-Month , no padding (9) 2-Month padded to 2 digits (09) 3-Month name abreviation (Sep) 4-Month name (September) 5-Month name abreviation in uppercase (SEP) 6-Month name in uppercase (SEPTEMBER) 7-Month name abreviation in lowercase (sep) 8-Month name in lowercase (september) 9-Month number in Roman numerals (IX)
c) Day formats (#printDayWithFormat:)
Saturday, December 1 2012 Â Â 1-Day of the month, no padding (1) 2-Day of the month padded to 2 digits (01) 3-Abbreviated day of week (Sat) 4-Complete day of week (Saturday) 5-Abbreviated day of week in uppercase (SAT) 6-Complete day of week in uppercase (SATURDAY) 7-Abbreviated day of week in lowercase (sat) 8-Complete day of week lowercase (saturday) 9-Day of the month with english suffix (1st) 10-Day of the year (336) 11-Day of the year with English suffix (336th) 12-Day of the week index [0=sunday 6 = saturday] (6) 13-Day of the week index [1=sunday 7 = saturday] (7) 14-Day of the week index [0=monday 6 = sunday] (5) 15-Day of the week index [1=monday 7 = sunday] (6) 16-Julian day, i.e. days since January 1, 4712 BC (2456263)
d) Week formats (#printWeekWithFormat:)
1-Week of the year (1..53) where Sunday if the first day of the week 2-Week of the year (1..53) where Monday if the first day of the week
e) Era formats (#printEraWithFormat:)
1-Era AD or BC 2-Era A.D. or B.C. 3-Era ad or bc 4-Era a.d. or b.c.
f) Century formats (#printCenturyWithFormat:)
1-Century (20) 2-Century with English suffix (20th)
 ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Bonjour Stéphane, I seem to have found the cause of the problem with Locale and translation : http://code.google.com/p/pharo/issues/detail?id=2424 Is this migration to gettext still "en route" and active? Was it abandoned? If we want a truly multilingual Pharo (and/or at least provide support for translation), we should definitely start looking at this very seriously! What do you think? Anyone working on this localization/translation stuff ?  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Bonjour Stéphane,
I seem to have found the cause of the problem with Locale and translation : http://code.google.com/p/pharo/issues/detail?id=2424
Is this migration to gettext still "en route" and active? Was it abandoned?
No abandoned but not top priority.
If we want a truly multilingual Pharo (and/or at least provide support for translation), we should definitely start looking at this very seriously!
what does it mean truly? Stef
What do you think?
Anyone working on this localization/translation stuff ?
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
What does it mean truly?   Well, I guess more and more people would make their apps multilingual if they had a localization/translation framework. I guess this is especially true in Europe (and in Quebec for sure!) but also in many specific parts of the USA (for instance in Texas I guess one would want to support English and Spanish at least).
From a functionality standpoint, not having a localization/translation framework is not a show-stopper since it looks like almost everyone understands English on this planet! But it would be nice to be able to provide apps in our native language and in other languages end users would want.
I guess we should at least start talking and thinking about it so that when comes the time to work on this, we'd already know where we're heading and how we'd do it. What do you think? Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
________________________________ From: Stéphane Ducasse <stephane.ducasse@inria.fr> To: Benoit St-Jean <bstjean@yahoo.com> Cc: "Pharo-project@lists.gforge.inria.fr" <Pharo-project@lists.gforge.inria.fr> Sent: Sunday, October 28, 2012 6:08:26 PM Subject: Re: Localization and translation
Bonjour Stéphane,
I seem to have found the cause of the problem with Locale and translation :Â http://code.google.com/p/pharo/issues/detail?id=2424
Is this migration to gettext still "en route" and active? Was it abandoned?
No abandoned but not top priority.
If we want a truly multilingual Pharo (and/or at least provide support for translation), we should definitely start looking at this very seriously!
what does it mean truly?
Stef
What do you think?
Anyone working on this localization/translation stuff ?
 ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
On 28.10.2012 21:37, Benoit St-Jean wrote:
Bonjour Stéphane,
I seem to have found the cause of the problem with Locale and translation : http://code.google.com/p/pharo/issues/detail?id=2424
Is this migration to gettext still "en route" and active? Was it abandoned?
If we want a truly multilingual Pharo (and/or at least provide support for translation), we should definitely start looking at this very seriously!
What do you think?
Anyone working on this localization/translation stuff ?
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Gettext is purely for translating and still exists afaik, as an external package. Rationale at the time being that translations don't belong in a core image, but rather support for them loaded if one is developing a multi-language application. Localization support in the sense of getting numbers/dates etc. printed correctly is fairly basic, limited to what you see in the Locale class. Obviously, this isn't good enough for, say, a webapp whose consumers aren't tied to the current system locale, for that interfacing the CLDR has been suggested, but not prioritized by anyone. Cheers, Henry
Hello, A really good package for everything related to Locales, translation and I18N is ICU [1]. I use the C version of this library through NativeBoost. Currently only part of the functionality is available in Smalltalk but this can easily be extended. Jan. [1] http://site.icu-project.org/ [2] http://ss3.gemstone.com/ss/ICU.html/Overview / http://ss3.gemstone.com/ss/ICU-V2.html/Overview On Mon, Oct 29, 2012 at 2:20 AM, Henrik Sperre Johansen < henrik.s.johansen@veloxit.no> wrote:
On 28.10.2012 21:37, Benoit St-Jean wrote:
Bonjour Stéphane,
I seem to have found the cause of the problem with Locale and translation : http://code.google.com/p/pharo/issues/detail?id=2424
Is this migration to gettext still "en route" and active? Was it abandoned?
If we want a truly multilingual Pharo (and/or at least provide support for translation), we should definitely start looking at this very seriously!
What do you think?
Anyone working on this localization/translation stuff ?
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
Gettext is purely for translating and still exists afaik, as an external package. Rationale at the time being that translations don't belong in a core image, but rather support for them loaded if one is developing a multi-language application.
Localization support in the sense of getting numbers/dates etc. printed correctly is fairly basic, limited to what you see in the Locale class. Obviously, this isn't good enough for, say, a webapp whose consumers aren't tied to the current system locale, for that interfacing the CLDR has been suggested, but not prioritized by anyone.
Cheers, Henry
On 28 Oct 2012, at 11:08, Benoit St-Jean <bstjean@yahoo.com> wrote:
Comments, complaints and suggestions are welcome!
Both formatting AND (strict) parsing should be provided, symmetrically. Names of months and weekdays should be translatable into arbitrary languages, probably other aspects as well, like AM/PM or BC⦠Timezones have various names as well (Europe/Brussels, CEST, Central European Time). Offset to timezone mapping is not unique. All in all, not easy. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
participants (8)
-
Benoit St-Jean -
Camillo Bruni -
Dale Henrichs -
Denis Kudriashov -
Henrik Sperre Johansen -
Jan van de Sandt -
Stéphane Ducasse -
Sven Van Caekenberghe