Hi,
ISC Edwin Cruz wrote:
> What abaut config files from smarty?
> http://smarty.php.net/manual/en/language.config.variables.php
>
> It would be similar to the first solution, also we could personalize colors,
> fonts, etc.
Fonts, colors, etc are a separate matter. I have looked at using smarty
config files in the past, but I want to be able to use these translated
files from outside of smarty.
Best Regards,
/bryan
>
> I hope that it might be usefull.
>
> Regards!
>
> +-------------------------------------+
> | ISC Edwin Cruz <ecruz@stripped> | +----+
> | System's Manager | | |
> | Transportes Medel Rogero SA de CV | | |
> | Desk: +52 (449) 910 30 90 x3054 | +----+
> | Aguascalientes, Mexico |
> | http://www.medel.com.mx |
> +-------------------------------------+
>
>
>
> -----Mensaje original-----
> De: Bryan Alsdorf [mailto:bryan@stripped]
> Enviado el: Miércoles, 25 de Enero de 2006 12:09 a.m.
> Para: morris32@stripped; m.vanderlinden@stripped;
> streamlake@stripped; list@stripped; ecruz@stripped
> CC: eventum-devel@stripped
> Asunto: Localization Plans
>
>
> Hi,
>
> I decided to move this discussion to the eventum-devel list.
>
> Originally our plans were to use gettext and the smarty-gettext plugin
> to localize Eventum. However, we would still need our own code to handle
> longer strings (as discussed here:
> http://lists.mysql.com/eventum-users/2735)
>
> The more I look at gettext, the more complicated it seems. I am now
> leaning towards using a simpler method. Instead of PO files, translated
> strings would be stored in PHP files, similar to this:
>
> == en_US ==
> $_LANG['welcome_string'] = "Hello";
>
> == ru_RU ==
> $_LANG['welcome_string'] = "Privet";
>
> The template files would use something like {translate
> name="welcome_string"}
>
> With gettext, the file (with an extension of PO) would look like this:
>
> msgid "Hello"
> msgstr "Privet"
>
> We would then have to run a program to translate the PO file to a binary
> format that gettext uses (a MO file).
>
> The template file would look like {t}Hello{/t}.
>
> In my mind, the first solution seems much simpler to me. We don't need
> to worry about gettext or having two translation sources (one for normal
> strings, one for longer strings).
>
> Does anyone have any comments or opinions on this?
>
> Best Regards,
--
Bryan Alsdorf, Software Engineer
MySQL AB, www.mysql.com
Are you MySQL certified? www.mysql.com/certification
