<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body >Team,
<br>
<br>I am sorry but I am not willing to take this up for vtiger CRM 5.0 .
<br>I would suggest that we take this up for 5.0.1.
<br>
<br>We have enough number of issues/features to test out.
<br>This will be an overhead as of now.
<br>
<br>I would rather invest time in testing the existing features/bugs.
<br>
<br>Requesting your understanding,
<br>
<br>Richie
<br>
<br><br><br><br><br><br>---- Sergio A. Kessler<sergiokessler@gmail.com> wrote ---- <br><br><blockquote style='border-left: 2px solid #0000FF; padding: 6px;'><html>
<xbody>
well, mike was trying to provide a migration path between the old and<br>new methods...<br><br>my approach would be simpler:<br><br>- I will not touch the database<br>- I will not provide a migration path (altough both methods of<br>translating can coexist for a time)<br><br>the patch will consist in a new file and a function, nothing more...<br>and if you do not use the new method of translation, everything will<br>run like before, so the patch is not disruptive at all...<br><br>do we agree on doing this ?<br><br><br>/sak<br><br>On 5/12/06, Abos <webmaster@vtigercrmfrance.org> wrote:<br>> This is the instructions sended by Mike himself, i paste the original<br>> message.<br>><br>><br>> I've tried to boil this down simply. Here's what you need.<br>><br>> 1) Extract these files in a directory named *locale/* inside your<br>> vtiger directory.<br>> 2) You need a table in vtiger named *lang_keys*. To create this,<br>> execute as follows (from the root vtiger directory):<br>> php locale/buildLangKeys.php<br>> This will create:<br>> locale/vtiger.pot (POT file for translating)<br>> locale/lang_keys.sql (initialization for the database table)<br>> The lang_keys.sql in the distributed file is actually the correct file<br>> from the alpha. However, you can rebuild if you like<br>> 3) I haven't reviewed where this is in 5.0, but the functions in<br>> utils_lang.php need to replace the same functions in the new 5.0<br>> utils.php (or wherever it is).<br>> 4) I've include a *4.2.3* version of the en_US and fr_FR translations.<br>> These need to be updated for 5.0. They are included for your reference.<br>><br>> Here's how the system works:<br>> 1) The following functions *return* the identical strings they used to:<br>> function return_app_list_strings_language($language)<br>> function return_application_language($language)<br>> function return_module_language($language, $module)<br>> They use the lang_keys database to build the contents of the strings,<br>> but instead of returning the English (which is in the database), they<br>> return _(English) making it translated.<br>> 2) Otherwise, system functions as expected. All new entries, however,<br>> can simply be _(*My New Strings*) rather than going to the complication<br>> of adding to mod_strings, etc.<br>><br>> Caveats:<br>> 1) There are several untranslated strings I had to find. I'll compile a<br>> list and provide later.<br>> 2) Squirrelmail is way screwed up. In it, it prints _($mod_strings[]),<br>> which causes lots of problems. I have fixed in my version, and will<br>> supply by Friday.<br>><br>> Future:<br>> 1) I will have a tool shortly which builds a PO file from an existing<br>> translation. This will be extremely useful in migrating from the old<br>> system to the new system.<br>><br>> Geek Alert:<br>> 1) If you really want to see something cool, look at buildLangKeys.txt<br>> and see how I am importing each language file, then assigning it to a<br>> string in an array from the import. Very cool.<br>><br>> This should be very clear, I hope. I will be on road a lot tomorrow.<br>> You can try to IM me, and I'll respond if I am free.<br>><br>> Cheers!<br>> Mike<br>><br>> P.S. I will post this to forge<br>><br>><br>><br>> Sergio A. Kessler a écrit :<br>> > yes, please, send it to this list...<br>> > (I do not like private messages)<br>> ><br>> > but I need confirmation that the patch (ie. the work) will not end in<br>> > the floor...<br>> > (if the patch is simple to merge, that is)<br>> ><br>> > /sak<br>> ><br>> > On 5/11/06, Abos <webmaster@vtigercrmfrance.org> wrote:<br>> ><br>> >> Sergio,<br>> >> Mike Crowe has sended me latest version of his gettext patch, i can mail<br>> >> you that if you want.<br>> >><br>> >><br>> >> Sergio A. Kessler a écrit :<br>> >><br>> >>> I'm short on time, but I can give it a try this weekend,<br>> >>> but the patch enabling gettext will be accepted or is too late ?<br>> >>><br>> >>> 1) the patch should be short<br>> >>> 2) the current translations can be mantained in the transition, I see<br>> >>> no problem in enabling gettext strings each by one<br>> >>><br>> >>> regards,<br>> >>> /sak<br>> >>><br>> >>> On 5/11/06, Abos <webmaster@vtigercrmfrance.org> wrote:<br>> >>><br>> >>><br>> >>>> Hi Sergio,<br>> >>>> do not miss understand (i know my english is poor),<br>> >>>> i'm not against gettext, if you have capabilitie to provide gettext<br>> >>>> support for vtiger crm 5 in short time, i provide french pack in pot<br>> >>>> format without any problem in same time.<br>> >>>> But i think before gettext integration, we have to ask to the<br>> >>>> translaters, to know their capabilities.<br>> >>>> Regards,<br>> >>>> Aïssa<br>> >>>><br>> >>>> Sergio A. Kessler a écrit :<br>> >>>><br>> >>>><br>> >>>>> aisa, is a lot more probably that you *gain* translators instead of<br>> >>>>> loosing them...<br>> >>>>> (I don't know how you came to that conclusion)<br>> >>>>><br>> >>>>> don't be afraid of gettext, the day you know it, you will wonder why<br>> >>>>> this thing hasn't used before...<br>> >>>>><br>> >>>>> gettext doesn't resolve the harcoded strings problems,<br>> >>>>> BUT it makes the task of mark a string to be tranlated SO easy, that's<br>> >>>>> is not even funny...<br>> >>>>><br>> >>>>> all you have to do is to change something from:<br>> >>>>><br>> >>>>> echo "harcoded string";<br>> >>>>><br>> >>>>> to<br>> >>>>><br>> >>>>> echo _("translatable string");<br>> >>>>><br>> >>>>> then you run a script that does all the dirty work for you...<br>> >>>>> and voilé, you have all the diccionaries updated and sinchronized...<br>> >>>>><br>> >>>>><br>> >>>>><br>> >>>>> On 5/10/06, Abos <webmaster@vtigercrmfrance.org> wrote:<br>> >>>>><br>> >>>>><br>> >>>>><br>> >>>>>> ok,<br>> >>>>>> Translate on array is boring, but really easy, using tool like poedit...<br>> >>>>>> is another thing (not really difficult i agree).<br>> >>>>>> But i prefer translate on php files and have vtiger CRM 5 may be for<br>> >>>>>> june than wait 2 more months and have gettext.<br>> >>>>>> Gettext doesn't resolve all the harcode problems (please confim).<br>> >>>>>> And before make the change, we have to train/inform the translators,<br>> >>>>>> loose some translators (and lang so) during the change is not good.<br>> >>>>>> Aïssa<br>> >>>>>><br>> >>>>>> Sergio A. Kessler a écrit :<br>> >>>>>><br>> >>>>>><br>> >>>>>><br>> >>>>>>> gettext is an order of magnitude easier to use for translators (than<br>> >>>>>>> an array based aproach) if you use poedit.<br>> >>>>>>><br>> >>>>>>> <a href="http://www.poedit.org/">http://www.poedit.org/</a><br>> >>>>>>><br>> >>>>>>> and I do not want to mention that gettext produces and keep<br>> >>>>>>> sincronized the files to translate automagically...<br>> >>>>>>><br>> >>>>>>> /sak<br>> >>>>>>><br>> >>>>>>> On 5/10/06, Abos <webmaster@vtigercrmfrance.org> wrote:<br>> >>>>>>><br>> >>>>>>><br>> >>>>>>><br>> >>>>>>><br>> >>>>>>>> Hi all,<br>> >>>>>>>> this is a small report for today svn snapshot.<br>> >>>>>>>><br>> >>>>>>>> Homepage : latest activities added layer appear (see screenshot), i<br>> >>>>>>>> think you know already.<br>> >>>>>>>><br>> >>>>>>>> Tab marketing, subtab account & contact, if i add an task/activitie, the<br>> >>>>>>>> redirection goes to tab support, the good subtab. (very small problem)<br>> >>>>>>>><br>> >>>>>>>> Tab "More information", when i translate close (for task/events) the<br>> >>>>>>>> table is not correctly displyed, miss the cell for close (X).<br>> >>>>>>>><br>> >>>>>>>> The compose email pop up, is just a little to small (need 50px weight more),<br>> >>>>>>>><br>> >>>>>>>> Problem with ' in company field information (alway),<br>> >>>>>>>><br>> >>>>>>>> When i send an email to a lead or contact, lead/contact description<br>> >>>>>>>> added to mail body. Very very very bad ! Imagine my comment, "fucking<br>> >>>>>>>> guy, dislike to work with him, bad debtor". Ouch !<br>> >>>>>>>><br>> >>>>>>>> Can't change invoices status, quotes /SO/PO stage on picklist settings<br>> >>>>>>>> (i think you just need time for quotes/SO/PO, but for the invoices, it's<br>> >>>>>>>> miss since 4.x)<br>> >>>>>>>><br>> >>>>>>>> Migration script alway break the install, i have make a test with a new<br>> >>>>>>>> and clean vtiger crm 4.2.3 database (without adding any data), only 4<br>> >>>>>>>> tables created : *actionmapping, announcement, field_seq,<br>> >>>>>>>> profile2globalpermissions.<br>> >>>>>>>><br>> >>>>>>>> *Brand question (i think to saint ?) why design the tiger pound to left<br>> >>>>>>>> on rss, calendar, email module ? The vtiger logo use a pount inclined to<br>> >>>>>>>> right.<br>> >>>>>>>><br>> >>>>>>>> Migration question :<br>> >>>>>>>> Why not provide migration script during install ? With user choice<br>> >>>>>>>> install/upgrade.<br>> >>>>>>>><br>> >>>>>>>> Loggin question : The logs make vtiger CRM slow, why not put loggin to<br>> >>>>>>>> WARN for stable version ?<br>> >>>>>>>><br>> >>>>>>>> Adding 1 more field to calls/meetings for incoming/outgoing can be very<br>> >>>>>>>> good.<br>> >>>>>>>><br>> >>>>>>>> Now the good things :)<br>> >>>>>>>> New really impressive design for the calendar, very very good !<br>> >>>>>>>> The quick create function can be a killer feature on vtiger 5 (time<br>> >>>>>>>> winning!!!)!<br>> >>>>>>>> The search engine is very cool, now we can search on entire system.<br>> >>>>>>>> The report module !!!! Ouch !!!! USABLE ! (Richie forgot what i have<br>> >>>>>>>> said about report module ;) )<br>> >>>>>>>> New real effort for translaters, thankkkksssssss, i am impatient to see<br>> >>>>>>>> vtiger crm 5 full french (and all french users too) !<br>> >>>>>>>> MSG to Richie, you say about i18n on forum: " Yes, we do need help.",<br>> >>>>>>>> what kind of help ? Harcode string feedback ? Moving harcode to lang<br>> >>>>>>>> file and give a patch ?... I'm ready.<br>> >>>>>>>><br>> >>>>>>>> About gettext, the problem with gettext, is you can loose translaters,<br>> >>>>>>>> gettext is more difficult to use, but more efficient. We need a full<br>> >>>>>>>> translate of vtiger CRM 5 (not 6). So for now, it's the right decision.<br>> >>>>>>>><br>> >>>>>>>> Conclusion : vtiger crm 5 is on the right way, look good, smell good.<br>> >>>>>>>> And i'm really enthusiastic(not sure for this word)<br>> >>>>>>>> I hope the plug-ins with same quality.<br>> >>>>>>>> Aïssa,<br>> >>>>>>>> gone to write a news on vtiger france<br>> >>>>>>>><br>> >>>>>>>><br>> >>>>>>>> _______________________________________________<br>> >>>>>>>><br>> ><br><br>_______________________________________________<br>This vtiger.com email is sponsored by Zoho Planner. Still scribbling down your To-Do's on bits of paper & palms of your hands? Try the AJAX enabled, personal organizer online, Zoho Planner for FREE instead! <a href="http://zohoplanner.com/?vt">http://zohoplanner.com/?vt</a> <br>
</xbody>
</html></blockquote></body></html>