Re: [Pharo-users] I18n in pharo

2017-11-13 Thread Hilaire
Ok, got it. Le 12/11/2017 à 13:04, Stephane Ducasse a écrit : Yes. Morph and Polymorph as well as Athens but Sparta offers a similar API. So conversion should be easy. And Bloc opens a lot of possibilities. Bloc is the result of around 4 years of effort understanding the domain and comparing

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Pavel Krivanek
2017-11-12 13:02 GMT+01:00 Stephane Ducasse : > Excellent Pavel. This is great. > So I do not get it. What is then not working? > The layout of the menu is wrong and everything needs to be proven with the newer versions of the dependent packages. -- Pavel > > Stef > >

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Stephane Ducasse
Hilaire Bloc, Brick are not in Pharo yet. So either you want to build on top of Bloc and you use Bloc or not. Easy. Right now in Pharo we have - plain Morphic (with Polymorph but this is the same) - Spec to build user interface independent of the underlying layer (Morphic for now) - Glamour to

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Stephane Ducasse
> Looks like a big sandwich, though. > > Will Athne be throwm away? With Polymorph and Morph? Yes. Morph and Polymorph as well as Athens but Sparta offers a similar API. So conversion should be easy. And Bloc opens a lot of possibilities. Bloc is the result of around 4 years of effort

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Stephane Ducasse
Excellent Pavel. This is great. So I do not get it. What is then not working? Stef On Sun, Nov 12, 2017 at 12:13 AM, Pavel Krivanek wrote: > > > 2017-11-10 11:52 GMT+01:00 Hilaire : >> >> A cleaner Pharo will help there. >> >> To be frank, I found

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Hilaire
I guess you used the latest source code version, which was reto-porting to P3. The prior one should get you a correct layout. Le 12/11/2017 à 00:13, Pavel Krivanek a écrit : To run DrGeo on Pharo 7 is not hard (see the screenshot) - of course it has some issues but they can be definitely

Re: [Pharo-users] I18n in pharo

2017-11-12 Thread Hilaire
Likely your extracted list from the items I mentionned is contiguous :) Looks like a big sandwich, though. Will Athne be throwm away? With Polymorph and Morph? Le 11/11/2017 à 21:56, Aliaksei Syrel a écrit : Could you, please, explain in a bit more detail why do you think that Sparta, Bloc,

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread stephan
On 11-11-17 21:18, H. Hirzel wrote: On 11/11/17, stephan wrote: On 10-11-17 12:23, Cédrick Béler wrote: Plus I have the impression Morphic mess is about to be solved. There is still an awful lot of essential complexity in beautiful graphics and typography that is not going

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Hilaire
P6 is definitely a better IDE compare to previous version, and for coming Calypso looks fantastic, but P6 is a worst vehicle for a desktop application. There is much more code included and you are on your on to shrink/clean it to deploy your desktop application to make it looks and behave user

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread H. Hirzel
On 11/11/17, stephan wrote: > On 10-11-17 12:23, Cédrick Béler wrote: >> Plus I have the impression Morphic mess is about to be solved. > > There is still an awful lot of essential complexity in beautiful > graphics and typography that is not going away. Microsoft Word still >

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread stephan
On 10-11-17 12:23, Cédrick Béler wrote: Plus I have the impression Morphic mess is about to be solved. There is still an awful lot of essential complexity in beautiful graphics and typography that is not going away. Microsoft Word still cannot layout a paragraph of text after 34 years of

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Pavel Krivanek
(Smalltalk at: #ConfigurationOfGettext) project bleedingEdge load > >> > > >> > All 11 Tests are green so at least what is there should work. Check > >> > the world menu and the code. Load the "Foo" package from the same > repository > &g

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
> > It’s quite a moving target with so many fundamental changes (GIT being one, > Bootstrap another huge one). I would not call it moving target. The API changes slowly and we deprecate most of them. > But I have the opposite impression (of course I don’t have to maintain a big > project

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
Hilaire I think that Pharo is getting a lot more modular. Do you imagine that we can reload Morphic? That we have a minimal image that does not rely on the compiler? and that we can reload the compiler, SUnit and more. We will start another pass because we will run an experience to get

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
Marcus translate is incomplete and I would not focus on translating Pharo. I would prefer to improve the self documentation in english. Let us concentrate where we can get better. Stef On Fri, Nov 10, 2017 at 11:20 AM, Marcus Denker wrote: > > > On 10 Nov 2017, at 11:18,

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
tx hiliare for the feedback. On Fri, Nov 10, 2017 at 11:10 AM, Hilaire wrote: > You can go with http://smalltalkhub.com/#!/~PharoExtras/Gettext > > For non latin language you will have to provide extra font at load time. > > It works fine on DrGeo based on P3, wtih Latin,

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
ame >> > repository >> > to see something in the tools. The idea was to have support for MO and >> > PO files completely written in Smalltalk as well as tools that allow you >> > to find and translate internationalized text. >> > >> > But as

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Stephane Ducasse
is would require more work. I would still favour a fully > in Pharo written solution (following the gettext formats) but maybe for >performance reasons then also bind to libgettext using UFFI. > > > Hope this gives some insights on the current existing solutions/status. > > T

Re: [Pharo-users] I18n in pharo

2017-11-11 Thread Andrew Glynn
, November 10, 2017 6:09 PM To: Any question about pharo is welcome Subject: RE: [Pharo-users] I18n in pharo I’d think about porting the I18n Gem from Ruby but replacing Gettext with xliff to be a better, more generalized solution.  Cascade in the Ruby Gem is a useful feature missing from other

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread Andrew Glynn
: [Pharo-users] I18n in pharo The Pharo 7/8 roadmap does not (yet) include I18N: https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Pharo7/ROADMAP.md and the Pharo core image still includes the "NaturalLanguageTranslator" solution still from Squeak. See this class for mo

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread Cédrick Béler
> > A cleaner Pharo will help there. > > To be frank, I found later Pharo releases not inspiring. Bigger, bigger and > bigger with added code, protocol changes, and bugs at will. It is becoming > too complicated for a hobby use of it. It’s quite a moving target with so many fundamental

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread H. Hirzel
Maybe in a different thread... On 11/10/17, H. Hirzel wrote: > On 11/10/17, Hilaire wrote: >> A cleaner Pharo will help there. >> >> To be frank, I found later Pharo releases not inspiring. Bigger, bigger >> and bigger with added code, protocol

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread H. Hirzel
On 11/10/17, Hilaire wrote: > A cleaner Pharo will help there. > > To be frank, I found later Pharo releases not inspiring. Bigger, bigger > and bigger with added code, protocol changes, and bugs at will. It is > becoming too complicated for a hobby use of it. > > I decided I

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread Hilaire
A cleaner Pharo will help there. To be frank, I found later Pharo releases not inspiring. Bigger, bigger and bigger with added code, protocol changes, and bugs at will. It is becoming too complicated for a hobby use of it. I decided I will not finish porting DrGeo to P6 or P7, and it will

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread Marcus Denker
> On 10 Nov 2017, at 11:18, Esteban Lorenzano wrote: > > > >> On 10 Nov 2017, at 04:05, Pavel Krivanek > > wrote: >> >> >> >> 2017-11-09 23:50 GMT+01:00 Esteban Lorenzano >

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread Esteban Lorenzano
rld menu and the code. Load the "Foo" package from the same repository > > to see something in the tools. The idea was to have support for MO and PO > > files completely written in Smalltalk as well as tools that allow you > > to find and translate internatio

Re: [Pharo-users] I18n in pharo

2017-11-10 Thread stephan
On 09-11-17 21:29, Викентий Потапов wrote: Will Pharo 7 be ready for i18n of applications? With QCMagritte we have provided string translations since Pharo 4 or so. In a Magritte-based application you can just add a visitor that walks the descriptions and extracts what needs translating. We

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Pavel Krivanek
ork. I would still favour a > fully in Pharo written solution (following the gettext formats) but maybe > for > > performance reasons then also bind to libgettext using UFFI. > > > > > > Hope this gives some insights on the current existing solutions/status. > >

[Pharo-users] i18n in Pharo

2017-11-09 Thread Викентий Потапов
Thanks all for a feedback! I really feel that i'm not alone :) > Vikenti did you check the Entreprise Pharo book because it contains > nice chapters from svn on cahracter encoding. Thank you, i'll take a look at this chapter. And i'll look at gettext. > Did you report it? Yes, i reported it

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Esteban Lorenzano
ybe for > performance reasons then also bind to libgettext using UFFI. > > > Hope this gives some insights on the current existing solutions/status. > > Thanks > Torsten > > >> Gesendet: Donnerstag, 09. November 2017 um 21:29 Uhr >> Von: "Викентий Потап

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Torsten Bergmann
2017 um 21:29 Uhr > Von: "Викентий Потапов" <vikenti.pota...@gmail.com> > An: pharo-users@lists.pharo.org > Betreff: [Pharo-users] I18n in pharo > > > Will Pharo 7 be ready for i18n of applications? > I mean some simple and useful way like in Cincom Visual Work

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Denis Kudriashov
In my experience I used my own custom implementation to support multiple languages. It was based on super simple dictionary of lang->labelName->text. I loaded it from custom xml file. My problem was that I never understood how gettext is supposed to be used on Windows. 2017-11-09 21:29 GMT+01:00

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Denis Kudriashov
Hi 2017-11-09 22:15 GMT+01:00 Stephane Ducasse : > Hi vikenti > > I would love. Now if nobody using a different alphabet does not give > us feedback and help we will not really make progress. > Denis how do you it? > I got this kind of errors in past with Pharo 1 on

Re: [Pharo-users] I18n in pharo

2017-11-09 Thread Stephane Ducasse
Hi vikenti I would love. Now if nobody using a different alphabet does not give us feedback and help we will not really make progress. Denis how do you it? Hilaire is using gettext or something like that in DrGeo. Vikenti did you check the Entreprise Pharo book because it contains nice chapters

[Pharo-users] I18n in pharo

2017-11-09 Thread Викентий Потапов
Will Pharo 7 be ready for i18n of applications? I mean some simple and useful way like in Cincom Visual Works, where translation dictionaries are separated from code and could be dinamycally changed without changing my application. It is very important for huge commercial applications,