Hi Georg,
Georg wrote:
seaBreeze which is a well-known extension to Seaside comes with Internationalization pre-built in and specially for you with German translations.
I know it - unfortunately the direct download is gone. :(
No need for german on my side, does SeaBreeze support Bidi (RTL/LTR)?
It ships with VisualWorks 7.10
Thanks - but installing VW just for a short look is overkill. Why was it removed?
I guess it uses some I18N stuff from VW anyway and I'm running on Pharo.
I can not use SeaBreeze for various reasons - one is that I want to have a "fresh look" with my http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap project (which could be interesting to modernize seaBreeze UI too and should be easy to port to VW if you like)
I found https://code.google.com/p/seaside/wiki/Gettext so far - but wanted to see what others use these days to easily support I18N in Seaside.
Thx T.
Hi Torsten
We use Gettext and Seaside-Gettext.
It does the job, though we are looking to extend it with strings that include variables (e.g. 'Welcome %s, today is a good day'). Right now, we just concatenate strings but that does not work very well. If anyone has already such a solution working with Gettext, I would be happy to know about it.
But it should not be difficult to add.
Johan
On 18 Oct 2013, at 08:53, "Torsten Bergmann" astares@gmx.de wrote:
I found https://code.google.com/p/seaside/wiki/Gettext so far - but wanted to see what others use these days to easily support I18N in Seaside.
On Fri, 18 Oct 2013, Johan Brichau wrote:
Hi Torsten
We use Gettext and Seaside-Gettext.
It does the job, though we are looking to extend it with strings that include variables (e.g. 'Welcome %s, today is a good day'). Right now, we just concatenate strings but that does not work very well.
I suggest you to use numbered parameters. We use #format: after translation, and it works well. The reason why numbered parameters are better is that the order of words can be very different in some languages, and swapping {1} with {2} is possible, while swapping %s with %s makes no sense :).
Levente
If anyone has already such a solution working with Gettext, I would be happy to know about it.
But it should not be difficult to add.
Johan
On 18 Oct 2013, at 08:53, "Torsten Bergmann" astares@gmx.de wrote:
I found https://code.google.com/p/seaside/wiki/Gettext so far - but wanted to see what others use these days to easily support I18N in Seaside.
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On 19 Oct 2013, at 00:20, Levente Uzonyi leves@elte.hu wrote:
I suggest you to use numbered parameters. We use #format: after translation, and it works well. The reason why numbered parameters are better is that the order of words can be very different in some languages, and swapping {1} with {2} is possible, while swapping %s with %s makes no sense :).
Indeed. This works very well and there is no need to add anything to Gettext for that.
Thanks for pointing that out. This is so obvious I wonder why I never saw it ;-)
Johan
seaside@lists.squeakfoundation.org