On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote:
On 26-Jan-2013, at 4:18 AM, Zoran Djordjevic <zo...@eu-build.com> wrote:
I was not so clear :)
In majority of project like this, multilingual is archived in following way:
1. There is table of all English strings used in the software
2. There is translation table for every language defining translation from English to language X
3. Strings are displayed using function like translate(language, string)
So, if you use something similar, and you have list of all strings, we, small language speakers, can simply fill this table for our language.and you can easily have as many languages as you want :)
It will also reduce need for custom Print Forms, because translation will be done automatically, especially if "language" became attribute of Print Form, Print Header, ...
Was that clear enough?
On Thursday, January 24, 2013 3:06:20 PM UTC+1, rushabh wrote: