Subject: Re: Xlations
From: Aaron Lehmann (aaronl@vitelus.com)
Date: Sat Jun 17 2000 - 15:43:01 CDT
Luddite :).
While what's visible to the end-user is very important, it is also
important to build a good architecture to make the software easy to expand
on and continue to develop. _("String") is simply easier than
AP_STRING_ID_... .
I don't really care very much, I'm just saying that I would prefer to use
gettext rather than our own mechanism so that developers such as myself
and translators can use the standard rather than learning and getting used
to Abi's proprietary one. I don't like code duplication very much. You can
probably see this in me in how I am pro-STL, pro-autoconf (compared to
make!).
Aaron Lehmann
> >>I second this. Gettext is the standard on Linux and it works very well.
> >>The one concern I have is how well this would be supported on platforms
> >>such as MacOS.
>
> This is another issue we've been through many times before.
>
> No, we do not have any plans to switch our i18n mechanism to use gettext.
> AbiWord is a *cross-platform* project, and we're just not going to always
> be able to use the APIs which are familiar to programmers on a specific
> platform.
>
> But the most important pushback on gettext is:
>
> Our current mechanism works fine. Changing it to gettext will not
> improve the experience for the end user. Why change it?
>
>
> Eric W. Sink, Software Craftsman
> SourceGear Corporation
> eric@sourcegear.com
>
>
>
>
>
This archive was generated by hypermail 2b25 : Sat Jun 17 2000 - 15:43:08 CDT