Re: [Tsheetx-developers] Internationalization (was: Spanish Translation)

[Scott M. <sco...@gm...>]

So, my opinion on committees is that they typically suck, and are very often
not needed.  Sure they are occasionally necessary, and there are times when
you need to bounce your ideas off someone else.  Fine, great, I understand
all that.

In this case, I'd rather not see this task die from "design by committee"
disease.  Anyone who's actually interested in helping to get TSNG to a point
where it is possible to provide translations to other languages just needs
to start somewhere and do it, preferably with solid standard practices.  As
I see it, the translation directory tree, English translation file, and a
single, already existing TSNG php file changed to use this translation file
should be checked in as the first step of this process.  From there, others
can take that work and begin to use that to "fix" the other files, one at a
time.  I'll (probably) even help, once it's started, but I don't have the
time or the drive to lead this charge, but I certainly support it.

Please post changes to this list or ask for SVN rights.

-Scott

On Thu, Aug 26, 2010 at 8:57 AM, Blaise Drayer <bl...@as...>wrote:

> Hi,
>
> > I'm not very experienced translating software, but a while ago I used
> http://translatewiki.net - it makes translation for software projects
> quite easy. I don't know how to add a project there, I just did some
> translations for a MediaWiki extension.
> > Maybe one of you can give it a try?
> > I'll be happy to assist translation into German at any time, for me excel
> sheets or text files are fine, too.
> > The problem I see is more related not to the menu items and messages, but
> to some localisation questions. In English, there are different formats for
> numbers, e. g. 2.5 in English is 2,5 in German (and Spanish as well I
> believe).
>
> There is many way to make a multi language website using constant,
> variable, Arrays, database, XML files, ...
>
> In all case there is a "Key" that is used for the translation.
>
> For example :
>
> $DailyTimesheet =  "Daily Timesheet";
> $Reports = "Reports"
> ...
>
> or
>
> define("DailyTimesheet","Daily Timesheet" ) ;
> define("Reports","Reports" ) ;
>
> All of this will be included in language files like fr.inc, en.inc,
> de.inc, ...
>
> So I think that the first thing to do is to defines the "Keys" and with
> time modify the code of Timesheet Next Gen to include this and also
> define what would be implemented for this on the code.
>
> I would propose to use Variables, Constants or Arrays for this. XML will
> also work but is a little bit more complicated because you manage the
> translations on the same files and need an additional library to do the
> job.
>
> The database is not an option on my point of view because it will cause
> many and many query per pages, ... But we can use a database to generate
> the translations, ...
>
> Best regards
>
> Blaise Drayer
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>