रवि भाई भी बता चुके हैं कि फ़यूल किस बला का नाम है...अब उसकी कुछ और फ़ोटो शोटो देखिए...
मानकीकरण के इस प्रयास को और भाषाओं के लिए भी शुरू करने की योजना है...फ़्यूल हिन्दी जारी किए जाने से आप परिचित तो हैं हीं...
Friday, July 25, 2008
Tuesday, July 22, 2008
Fuel : Means and End
After the public release of Fuel first language Hindi, lots of questions arises and need answers. I believe that these questions will certainly be valuable in giving Fuel a better shape and size. Some of the major aspects I tried to explain here...
1. Fuel is a Collaborative, Open and Transparent way to achieve standardization
Inclusiveness and participation are the backbone of Fuel process. It provides public review process in creating terms. It is having a version control system, bug tracker and ticketing system and a public mailing list through which anybody can take part in discussion about it. With the help of collaborative and open process Fuel is able to generate quality localized content.
2. Fuel should not be confused with a simple glossary
Though Fuel's 'end' is to come with a 'standardized' 'glossary' but the 'means' through this is evolving is entirely different. Here, as we shown for Hindi language, we are coming with a glossary by public evaluation by all the active communities, not only from Firefox or OpenOffice or Gnome or Kde localizers..., but all groups sat together at one place and discussed issues and finally decided that from now onwards we will use these 'standardized' entries only for the desktop translation these entries. Fuel is based on the consensus of active communities. So here comes the end of inconsistency!
3. Fuel considers whole desktop in totality
FUEL will be an attempt to put effort of standardization for desktop as a whole, desktop in totality instead of concentrating on different applications one by one. This approach has several benefit over others. One major benefit is that its usability is much more than others who take different applications individually. Also, for creating manuals it's benefit is big. It has nothing to do with the quantity of translation, it concentrates on giving consistently highly quality content.
4. Fuel is/can be the main catalyst, main fuel, main motivator behind a language having no terminology. If any language is not having terminology than Fuel is able to give a quick idea about the major entries that s/he is going to translate for her/his language. I, personally, think that language having no terminology should first concentrate on making at least primary level glossary. It is also making the review process easier. At present just 578 entries to start with!
1. Fuel is a Collaborative, Open and Transparent way to achieve standardization
Inclusiveness and participation are the backbone of Fuel process. It provides public review process in creating terms. It is having a version control system, bug tracker and ticketing system and a public mailing list through which anybody can take part in discussion about it. With the help of collaborative and open process Fuel is able to generate quality localized content.
2. Fuel should not be confused with a simple glossary
Though Fuel's 'end' is to come with a 'standardized' 'glossary' but the 'means' through this is evolving is entirely different. Here, as we shown for Hindi language, we are coming with a glossary by public evaluation by all the active communities, not only from Firefox or OpenOffice or Gnome or Kde localizers..., but all groups sat together at one place and discussed issues and finally decided that from now onwards we will use these 'standardized' entries only for the desktop translation these entries. Fuel is based on the consensus of active communities. So here comes the end of inconsistency!
3. Fuel considers whole desktop in totality
FUEL will be an attempt to put effort of standardization for desktop as a whole, desktop in totality instead of concentrating on different applications one by one. This approach has several benefit over others. One major benefit is that its usability is much more than others who take different applications individually. Also, for creating manuals it's benefit is big. It has nothing to do with the quantity of translation, it concentrates on giving consistently highly quality content.
4. Fuel is/can be the main catalyst, main fuel, main motivator behind a language having no terminology. If any language is not having terminology than Fuel is able to give a quick idea about the major entries that s/he is going to translate for her/his language. I, personally, think that language having no terminology should first concentrate on making at least primary level glossary. It is also making the review process easier. At present just 578 entries to start with!
Tuesday, July 15, 2008
फ़्यूल हिन्दी 12 जुलाई को जारी
फ़्यूल परियोजना की ओर से हिन्दी कंप्यूटर की बारंबार प्रयोग में आनेवाली प्रविष्टियों के एक मानक रूप की तलाश शायद समाप्त हुई लगती है. हिन्दी कंप्यूटर के मानकीकरण के प्रयास में परंपरागत प्रयासों से कुछ अलग हटकर फ़्यूल के प्रयास को एक बड़ी सफलता मिली है. व्यापक सामुदायिक मूल्यांकन के बाद फ़्यूल हिन्दी को गत रविवार को जारी किया गया है. कई अनुवादकों, भाषा के जानकार लोगों और स्थानीयकरण तकनीक से जुड़े धुंरधरों ने मिलकर फ़्यूल हिन्दी का मूल्यांकन कर उसे सार्वजनिक रूप से जारी किया. आप फ़्यूल हिन्दी के बारे में विस्तार से यहाँ पढ़ सकते हैं.
फ़्यूल की सबसे बड़ी ख़ासियत यह है कि यहाँ शब्द पर निर्णय खुले व साझेदारी से लिए जाते हैं. फिर इस परियोजना में आपको सूची के संबंध में अपनी शिकायत को दर्ज़ करने की भी सुविधा है. किसी दूसरे सॉफ़्टवेयर विकास की प्रक्रियाओं की तरह यहाँ भी सारी सुविधाएँ हैं और कोई भी व्यक्ति इससे जुड़ सकता है. सबसे महत्वपूर्ण रूप से, यहाँ पर एक पूरे डेस्कटॉप की समग्रता में देखने के कोशिश की गई है बजाए अलग अलग अनुप्रयोग के. यह निश्चित रूप से डेस्कटॉप स्थानीयकरण के मानकीकरण की ओर जाने में मदद करेगा. साथ ही वैसे लोगों की सुविधा के लिए मूल्यांकन किए गए फाइल को दूसरे रूप में भी रखा गया है जो पीओ प्रारूप से परिचित नहीं हैं. इसके अलावे वर्शन कंट्रोल सिस्टम व एक डाक सूची भी है.
दो दिनों तक लोगों ने मिल-बैठकर तय किया है कि भविष्य में इन प्रविष्टियों का स्वरूप स्थिर रखने की कोशिश की जाएगी...लेकिन माँग और आवश्यकता पड़ने पर हम तब्दीली भी जरूर करेंगे. साथ ही अनुप्रयोगों के नए संस्करणों के परिवर्तन को समाहित करने के लिए हम आवधिक रूप से इसे नए रूप में जारी करेंगे. लेकिन यह तो बाद की बात है...पहले हिन्दी फ़्यूल सूची pdf, ods या po में से किसी रूप में डाउनलोड कीजिए और अपने सुझाव इस फ़्यूल डाक सूची में शामिल होकर भेजिए.
फ़्यूल की सबसे बड़ी ख़ासियत यह है कि यहाँ शब्द पर निर्णय खुले व साझेदारी से लिए जाते हैं. फिर इस परियोजना में आपको सूची के संबंध में अपनी शिकायत को दर्ज़ करने की भी सुविधा है. किसी दूसरे सॉफ़्टवेयर विकास की प्रक्रियाओं की तरह यहाँ भी सारी सुविधाएँ हैं और कोई भी व्यक्ति इससे जुड़ सकता है. सबसे महत्वपूर्ण रूप से, यहाँ पर एक पूरे डेस्कटॉप की समग्रता में देखने के कोशिश की गई है बजाए अलग अलग अनुप्रयोग के. यह निश्चित रूप से डेस्कटॉप स्थानीयकरण के मानकीकरण की ओर जाने में मदद करेगा. साथ ही वैसे लोगों की सुविधा के लिए मूल्यांकन किए गए फाइल को दूसरे रूप में भी रखा गया है जो पीओ प्रारूप से परिचित नहीं हैं. इसके अलावे वर्शन कंट्रोल सिस्टम व एक डाक सूची भी है.
दो दिनों तक लोगों ने मिल-बैठकर तय किया है कि भविष्य में इन प्रविष्टियों का स्वरूप स्थिर रखने की कोशिश की जाएगी...लेकिन माँग और आवश्यकता पड़ने पर हम तब्दीली भी जरूर करेंगे. साथ ही अनुप्रयोगों के नए संस्करणों के परिवर्तन को समाहित करने के लिए हम आवधिक रूप से इसे नए रूप में जारी करेंगे. लेकिन यह तो बाद की बात है...पहले हिन्दी फ़्यूल सूची pdf, ods या po में से किसी रूप में डाउनलोड कीजिए और अपने सुझाव इस फ़्यूल डाक सूची में शामिल होकर भेजिए.
Fuel because...
Fuel (Frequently Used Entries for Localization) because... there are lot of problem users are facing when using softwares localized in their own languages. And so they, fade up with the 'quality' of translation, are commenting regularly on the 'translators'. On the other hand translators think it nothing more than a 'thankless' job. Actually all major desktop related entries appearing on menus and sub-menus are not more than five-six hunderd. So if we move to standardize a mere 500-600 entries and the process is backed by the active localizers and entities who get benefit from localization then we can make a successful move against the problem of standardization and inconsistency in software translation. This is the main idea behind FUEL.
Generally lots of similar words are used for different applications with almost all having same context...like File, Edit, View, Save, Save as...!! Collecting all these words from different applications and putting it together can help much. Choosing entries from menus and sub-menus appearing on a desktop, its panel, browser, office suits, editor, email client, messanger and terminal and by concentrating on these entries only, we can get an amazing result instantly. But its only a start. No doubt, for software localization these five-six hundred entries are most vital and we can give a face-wash and make our destop 'fresh' from a 'tired' look. So these are the entries that are frequently used for localization and so I like to call it 'Fuel' ie. 'frequentlu used entries for localization'.
The effort of FUEL is unique. It is a set of steps any content generating people involved in creating localized content can undertake and with the help of this we can ensure consistently highly quality. Including this FUEL is having a version control system allowing evolution of terms, a bug tracker and ticketing system and a mailing list also. Collaborative innovation is a most important aspect. In the process finally it is able to allow inclusiveness and participation with openness and transparency.
The history of standardization contains lot of major names and contributors inside it. But these standardization efforts were generally automated. Generally after the long process and labour glossaries with several thousands of entries were made available to the public. But nothing changed! This doesn't mean that FUEL undermines the importance of previous works. But here in FUEL, effort will be more on collaboration and openness so as like earlier standardization efforts it not only comes as an addition to the existing chaos and making the standardization process finally more complex. The individual FUEL effort for different languages will generally start with smaller number of entries. Apart from these features it also provides public review process in creating terms. During the process of standardization, FUEL will be an attempt to put effort of standardization for desktop as a whole, desktop in totallity instead of concentrating on different applications one by one. So currentely we have incorporated entries from gnome desktop (gdm, panel, gnome-menu etc), gedit (editor) openoffice (office suit), firefox (Browser), evolution (Email Client), and pidgin (instant messanger) so that we can have all the entires that a normal user uses frequentely. By this way we tried to use representative entries from major application. If a people is changing the platform s/he will see similar or almost similar entries.
So, FUEL (Frequently Used Entries for Localization) aims at solving the Problem of Inconsistency and Lack of standardization in Computer Software Translation across the platform for all Indic Languages. It will try to provide a standardized and consistent look of computer for a language computer users.
Generally lots of similar words are used for different applications with almost all having same context...like File, Edit, View, Save, Save as...!! Collecting all these words from different applications and putting it together can help much. Choosing entries from menus and sub-menus appearing on a desktop, its panel, browser, office suits, editor, email client, messanger and terminal and by concentrating on these entries only, we can get an amazing result instantly. But its only a start. No doubt, for software localization these five-six hundred entries are most vital and we can give a face-wash and make our destop 'fresh' from a 'tired' look. So these are the entries that are frequently used for localization and so I like to call it 'Fuel' ie. 'frequentlu used entries for localization'.
The effort of FUEL is unique. It is a set of steps any content generating people involved in creating localized content can undertake and with the help of this we can ensure consistently highly quality. Including this FUEL is having a version control system allowing evolution of terms, a bug tracker and ticketing system and a mailing list also. Collaborative innovation is a most important aspect. In the process finally it is able to allow inclusiveness and participation with openness and transparency.
The history of standardization contains lot of major names and contributors inside it. But these standardization efforts were generally automated. Generally after the long process and labour glossaries with several thousands of entries were made available to the public. But nothing changed! This doesn't mean that FUEL undermines the importance of previous works. But here in FUEL, effort will be more on collaboration and openness so as like earlier standardization efforts it not only comes as an addition to the existing chaos and making the standardization process finally more complex. The individual FUEL effort for different languages will generally start with smaller number of entries. Apart from these features it also provides public review process in creating terms. During the process of standardization, FUEL will be an attempt to put effort of standardization for desktop as a whole, desktop in totallity instead of concentrating on different applications one by one. So currentely we have incorporated entries from gnome desktop (gdm, panel, gnome-menu etc), gedit (editor) openoffice (office suit), firefox (Browser), evolution (Email Client), and pidgin (instant messanger) so that we can have all the entires that a normal user uses frequentely. By this way we tried to use representative entries from major application. If a people is changing the platform s/he will see similar or almost similar entries.
So, FUEL (Frequently Used Entries for Localization) aims at solving the Problem of Inconsistency and Lack of standardization in Computer Software Translation across the platform for all Indic Languages. It will try to provide a standardized and consistent look of computer for a language computer users.
Subscribe to:
Posts (Atom)