Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

[TIP] Creating language dependent component ! 23 Nov 2011 14:08 #571

  • giori
  • giori's Avatar Topic Author
  • Offline
  • Senior Member
  • Senior Member
  • Posts: 73
  • Thank you received: 14
Hi everybody,

If you start creating your component in your own non english language, you will soon discover that many keywords in the generated language files will be in your own native language. Cook simply takes your text entries and creates keywords for the translation files. So you will get entries like:

PROJECT_FIELD_MONATS_KALENDER instead of PROJECT_FIELD_MONTHLY_CALENDAR

So from my experience now, it is advisable to create your component entirely in English, then all the keywords in the translation files will be properly set in English. So you can create your own language files at the end of the process. This is particularly important if you are going to distribute your component and want the Joomla community to create translation files for you.
The following user(s) said Thank You: admin

Please Log in or Create an account to join the conversation.

Last edit: by admin.

Re: [TIP] Creating language dependent component ! 25 Mar 2012 05:38 #1723

I would like to help in the development of the project added Russian localization
You interested?

Please Log in or Create an account to join the conversation.

Re: [TIP] Creating language dependent component ! 25 Mar 2012 15:10 #1725

I`m Portuguese speaker, but I always build my extensions in English, because we never know when our customer will want to go international... In this case I don`t really bother to have a portuguese version, because at the end, I just get the translation files and make it whant ever I need
Paulo Griiettner

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.119 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started