LST Translation proposal
Posted by Al
|
LST Translation proposal March 22, 2009 02:00AM |
Hello All
I should like to propose a possible process for the translation of the Windev LSt into English and ask for your comments.
I have subscribed to the LST in the past and struggled with trying to get the examples to work and eventually gave up, but a chance meeting with a French student and subsequent discussions regarding translation has sparked my interest again
I propose a fairly simple translation process to keep down the cost and also to make use of our own native intelligence to fill in any missing parts.
1. A group of us agree to split the cost of the translation and we create any programming tools as required.
2. Each member of the group would need to submit a copy of their invoice/order for the LST as proof of legitimate ownership.
3. Word for word translation of the articles and tips in the LST magazine. This is the hardest and most costly part, because to the best of my knowledge, PCSoft do not supply the text electronically, so someone has to translate and type it out again in English. How frustrating and archaic. Maybe it could be scanned and OCR ?
If PCsoft could be persuaded to supply the text electronically then the whole process would be much easier and their sales of the existing LST would surely improve.
4. We can use Windev to translate the code of each project into English
5. Code comments and statics with text - I am happy enough to use Google to translate these and paste them into the project myself - I have compared Google translations with an early copy of Systran Pro and Google is better - but others may prefer to have them fully translated.
6. I had already written a small program to produce a list of Hyper File field names used in a project and this could be used to produce a list for translation of the field names into English with accompanying captions. Using this list we could individually rename the field in the analysis for each LST project. Windev will re-write the code with the changed field names as part of the analysis change. The hyperfile field list program is on the WinDAsso site if anyone is interested in it.
To get the English captions into the project we could manually enter them or we could do it dynamically by holding the file/field/caption information in a data base and use a global proc or class to re-write the caption prompts as the project executes
This process will leave gaps in the projects that we would need to complete from our own endeavours but the combination of paid translation and our own efforts means that although as a group we would all pay for the translation of all the articles in each LST, we would only have to put further effort into those items that really were of interest.
Possible issues:
PCSoft's attitude to the idea. If there are enough interested forum members and we can come to an agreement on the process, then all we can do is ask PCSoft.
How would we handle latecomers to the initial group, in terms of their financial contribution ? This whole process should be non-profit making.
Where do we start - from which LST ?
Do we translate the entire LST or have a vote on the articles.
How do we communicate with each other - privately or via a sub forum to this forum ?
Do we form a new group of interested members for each LST or do we commit to a set number of LST issues as a group ?
How do we run the process, who handles the money ?
I think there is value to be gained for us from the LST and PCSoft do not seem to have any interest in the translation, possible due to the cost/revenue ratio, so I hope my comments will provoke a discussion that will lead to a firm proposal and process to make best use of the LST for English speaking users.
Regards
Al
I should like to propose a possible process for the translation of the Windev LSt into English and ask for your comments.
I have subscribed to the LST in the past and struggled with trying to get the examples to work and eventually gave up, but a chance meeting with a French student and subsequent discussions regarding translation has sparked my interest again
I propose a fairly simple translation process to keep down the cost and also to make use of our own native intelligence to fill in any missing parts.
1. A group of us agree to split the cost of the translation and we create any programming tools as required.
2. Each member of the group would need to submit a copy of their invoice/order for the LST as proof of legitimate ownership.
3. Word for word translation of the articles and tips in the LST magazine. This is the hardest and most costly part, because to the best of my knowledge, PCSoft do not supply the text electronically, so someone has to translate and type it out again in English. How frustrating and archaic. Maybe it could be scanned and OCR ?
If PCsoft could be persuaded to supply the text electronically then the whole process would be much easier and their sales of the existing LST would surely improve.
4. We can use Windev to translate the code of each project into English
5. Code comments and statics with text - I am happy enough to use Google to translate these and paste them into the project myself - I have compared Google translations with an early copy of Systran Pro and Google is better - but others may prefer to have them fully translated.
6. I had already written a small program to produce a list of Hyper File field names used in a project and this could be used to produce a list for translation of the field names into English with accompanying captions. Using this list we could individually rename the field in the analysis for each LST project. Windev will re-write the code with the changed field names as part of the analysis change. The hyperfile field list program is on the WinDAsso site if anyone is interested in it.
To get the English captions into the project we could manually enter them or we could do it dynamically by holding the file/field/caption information in a data base and use a global proc or class to re-write the caption prompts as the project executes
This process will leave gaps in the projects that we would need to complete from our own endeavours but the combination of paid translation and our own efforts means that although as a group we would all pay for the translation of all the articles in each LST, we would only have to put further effort into those items that really were of interest.
Possible issues:
PCSoft's attitude to the idea. If there are enough interested forum members and we can come to an agreement on the process, then all we can do is ask PCSoft.
How would we handle latecomers to the initial group, in terms of their financial contribution ? This whole process should be non-profit making.
Where do we start - from which LST ?
Do we translate the entire LST or have a vote on the articles.
How do we communicate with each other - privately or via a sub forum to this forum ?
Do we form a new group of interested members for each LST or do we commit to a set number of LST issues as a group ?
How do we run the process, who handles the money ?
I think there is value to be gained for us from the LST and PCSoft do not seem to have any interest in the translation, possible due to the cost/revenue ratio, so I hope my comments will provoke a discussion that will lead to a firm proposal and process to make best use of the LST for English speaking users.
Regards
Al
|
Re: LST Translation proposal March 23, 2009 01:09PM |
Hi Al,
I have a subscription to LST. Probably my french is not so good
(neither my english) but I think I can read and understand almost
everything so I'll be glad to try to make a translation of some
articles.
Please, keep me on your list.
Regards,
Le 23/03/2009, Al a supposé :
> Hello All
> I should like to propose a possible process for the translation of the Windev
> LSt into English and ask for your comments. I have subscribed to the LST in
> the past and struggled with trying to get the examples to work and eventually
> gave up, but a chance meeting with a French student and subsequent
> discussions regarding translation has sparked my interest again I propose a
> fairly simple translation process to keep down the cost and also to make use
> of our own native intelligence to fill in any missing parts. 1. A group of
> us agree to split the cost of the translation and we create any programming
> tools as required. 2. Each member of the group would need to submit a copy of
> their invoice/order for the LST as proof of legitimate ownership. 3. Word
> for word translation of the articles and tips in the LST magazine. This is
> the hardest and most costly part, because to the best of my knowledge, PCSoft
> do not supply the text electronically, so someone has to translate and type
> it out again in English. How frustrating and archaic. Maybe it could be
> scanned and OCR ? If PCsoft could be persuaded to supply the text
> electronically then the whole process would be much easier and their sales of
> the existing LST would surely improve. 4. We can use Windev to translate the
> code of each project into English 5. Code comments and statics with text - I
> am happy enough to use Google to translate these and paste them into the
> project myself - I have compared Google translations with an early copy of
> Systran Pro and Google is better - but others may prefer to have them fully
> translated. 6. I had already written a small program to produce a list of
> Hyper File field names used in a project and this could be used to produce a
> list for translation of the field names into English with accompanying
> captions. Using this list we could individually rename the field in the
> analysis for each LST project. Windev will re-write the code with the
> changed field names as part of the analysis change. The hyperfile field
> list program is on the WinDAsso site if anyone is interested in it. To get
> the English captions into the project we could manually enter them or we
> could do it dynamically by holding the file/field/caption information in a
> data base and use a global proc or class to re-write the caption prompts as
> the project executes
>
> This process will leave gaps in the projects that we would need to complete
> from our own endeavours but the combination of paid translation and our own
> efforts means that although as a group we would all pay for the translation
> of all the articles in each LST, we would only have to put further effort
> into those items that really were of interest. Possible issues: PCSoft's
> attitude to the idea. If there are enough interested forum members and we
> can come to an agreement on the process, then all we can do is ask PCSoft.
> How would we handle latecomers to the initial group, in terms of their
> financial contribution ? This whole process should be non-profit making.
> Where do we start - from which LST ? Do we translate the entire LST or have a
> vote on the articles. How do we communicate with each other - privately or
> via a sub forum to this forum ? Do we form a new group of interested members
> for each LST or do we commit to a set number of LST issues as a group ? How
> do we run the process, who handles the money ?
>
> I think there is value to be gained for us from the LST and PCSoft do not
> seem to have any interest in the translation, possible due to the
> cost/revenue ratio, so I hope my comments will provoke a discussion that will
> lead to a firm proposal and process to make best use of the LST for English
> speaking users.
>
> Regards
> Al
--
Mauricio
Copenhague, Dinamarca
Message forwarded from pcsoft.us.windev
I have a subscription to LST. Probably my french is not so good
(neither my english) but I think I can read and understand almost
everything so I'll be glad to try to make a translation of some
articles.
Please, keep me on your list.
Regards,
Le 23/03/2009, Al a supposé :
> Hello All
> I should like to propose a possible process for the translation of the Windev
> LSt into English and ask for your comments. I have subscribed to the LST in
> the past and struggled with trying to get the examples to work and eventually
> gave up, but a chance meeting with a French student and subsequent
> discussions regarding translation has sparked my interest again I propose a
> fairly simple translation process to keep down the cost and also to make use
> of our own native intelligence to fill in any missing parts.
1. A group of
> us agree to split the cost of the translation and we create any programming
> tools as required. 2. Each member of the group would need to submit a copy of
> their invoice/order for the LST as proof of legitimate ownership. 3. Word
> for word translation of the articles and tips in the LST magazine. This is
> the hardest and most costly part, because to the best of my knowledge, PCSoft
> do not supply the text electronically, so someone has to translate and type
> it out again in English. How frustrating and archaic. Maybe it could be
> scanned and OCR ? If PCsoft could be persuaded to supply the text
> electronically then the whole process would be much easier and their sales of
> the existing LST would surely improve. 4. We can use Windev to translate the
> code of each project into English 5. Code comments and statics with text - I
> am happy enough to use Google to translate these and paste them into the
> project myself - I have compared Google translations with an early copy of
> Systran Pro and Google is better - but others may prefer to have them fully
> translated. 6. I had already written a small program to produce a list of
> Hyper File field names used in a project and this could be used to produce a
> list for translation of the field names into English with accompanying
> captions. Using this list we could individually rename the field in the
> analysis for each LST project. Windev will re-write the code with the
> changed field names as part of the analysis change. The hyperfile field
> list program is on the WinDAsso site if anyone is interested in it. To get
> the English captions into the project we could manually enter them or we
> could do it dynamically by holding the file/field/caption information in a
> data base and use a global proc or class to re-write the caption prompts as
> the project executes
>
> This process will leave gaps in the projects that we would need to complete
> from our own endeavours but the combination of paid translation and our own
> efforts means that although as a group we would all pay for the translation
> of all the articles in each LST, we would only have to put further effort
> into those items that really were of interest. Possible issues: PCSoft's
> attitude to the idea. If there are enough interested forum members and we
> can come to an agreement on the process, then all we can do is ask PCSoft.
> How would we handle latecomers to the initial group, in terms of their
> financial contribution ? This whole process should be non-profit making.
> Where do we start - from which LST ? Do we translate the entire LST or have a
> vote on the articles. How do we communicate with each other - privately or
> via a sub forum to this forum ? Do we form a new group of interested members
> for each LST or do we commit to a set number of LST issues as a group ? How
> do we run the process, who handles the money ?
>
> I think there is value to be gained for us from the LST and PCSoft do not
> seem to have any interest in the translation, possible due to the
> cost/revenue ratio, so I hope my comments will provoke a discussion that will
> lead to a firm proposal and process to make best use of the LST for English
> speaking users.
>
> Regards
> Al
--
Mauricio
Copenhague, Dinamarca
Message forwarded from pcsoft.us.windev
|
Re: LST Translation proposal March 23, 2009 04:33PM |
Maybe PC Soft would reconsider making the LST magazine available in
electronic form to this project.
Have you contacted the publishers recently - times and attitudes change.
If they want to see how much interest is - they could make a "poll" and we
all can respond.
As a new person to WinDev\WebDev I would love to have a magazine like this
available to me in English.
--
Kevin Erskine
Software By Ragazzi
www.Software-By-Ragazzi.com
Alameda, CA (USA)
"Al" <guest@news.pcsoft.fr> wrote in message
news:61212009032308501866.24219@news.pcsoft.fr...
>
> Hello All
> I should like to propose a possible process for the translation of the
> Windev LSt into English and ask for your comments.
> I have subscribed to the LST in the past and struggled with trying to get
> the examples to work and eventually gave up, but a chance meeting with a
> French student and subsequent discussions regarding translation has
> sparked my interest again
> I propose a fairly simple translation process to keep down the cost and
> also to make use of our own native intelligence to fill in any missing
> parts.
> 1. A group of us agree to split the cost of the translation and we create
> any programming tools as required.
> 2. Each member of the group would need to submit a copy of their
> invoice/order for the LST as proof of legitimate ownership.
> 3. Word for word translation of the articles and tips in the LST
> magazine. This is the hardest and most costly part, because to the best
> of my knowledge, PCSoft do not supply the text electronically, so someone
> has to translate and type it out again in English. How frustrating and
> archaic. Maybe it could be scanned and OCR ?
> If PCsoft could be persuaded to supply the text electronically then the
> whole process would be much easier and their sales of the existing LST
> would surely improve.
> 4. We can use Windev to translate the code of each project into English
> 5. Code comments and statics with text - I am happy enough to use Google
> to translate these and paste them into the project myself - I have
> compared Google translations with an early copy of Systran Pro and Google
> is better - but others may prefer to have them fully translated.
> 6. I had already written a small program to produce a list of Hyper File
> field names used in a project and this could be used to produce a list for
> translation of the field names into English with accompanying captions.
> Using this list we could individually rename the field in the analysis for
> each LST project. Windev will re-write the code with the changed field
> names as part of the analysis change. The hyperfile field list program
> is on the WinDAsso site if anyone is interested in it.
> To get the English captions into the project we could manually enter them
> or we could do it dynamically by holding the file/field/caption
> information in a data base and use a global proc or class to re-write the
> caption prompts as the project executes
>
> This process will leave gaps in the projects that we would need to
> complete from our own endeavours but the combination of paid translation
> and our own efforts means that although as a group we would all pay for
> the translation of all the articles in each LST, we would only have to put
> further effort into those items that really were of interest.
> Possible issues:
> PCSoft's attitude to the idea. If there are enough interested forum
> members and we can come to an agreement on the process, then all we can do
> is ask PCSoft.
> How would we handle latecomers to the initial group, in terms of their
> financial contribution ? This whole process should be non-profit
> making.
> Where do we start - from which LST ?
> Do we translate the entire LST or have a vote on the articles.
> How do we communicate with each other - privately or via a sub forum to
> this forum ?
> Do we form a new group of interested members for each LST or do we commit
> to a set number of LST issues as a group ?
> How do we run the process, who handles the money ?
>
> I think there is value to be gained for us from the LST and PCSoft do not
> seem to have any interest in the translation, possible due to the
> cost/revenue ratio, so I hope my comments will provoke a discussion that
> will lead to a firm proposal and process to make best use of the LST for
> English speaking users.
>
> Regards
> Al
>
Message forwarded from pcsoft.us.windev
electronic form to this project.
Have you contacted the publishers recently - times and attitudes change.
If they want to see how much interest is - they could make a "poll" and we
all can respond.
As a new person to WinDev\WebDev I would love to have a magazine like this
available to me in English.
--
Kevin Erskine
Software By Ragazzi
www.Software-By-Ragazzi.com
Alameda, CA (USA)
"Al" <guest@news.pcsoft.fr> wrote in message
news:61212009032308501866.24219@news.pcsoft.fr...
>
> Hello All
> I should like to propose a possible process for the translation of the
> Windev LSt into English and ask for your comments.
> I have subscribed to the LST in the past and struggled with trying to get
> the examples to work and eventually gave up, but a chance meeting with a
> French student and subsequent discussions regarding translation has
> sparked my interest again
> I propose a fairly simple translation process to keep down the cost and
> also to make use of our own native intelligence to fill in any missing
> parts.
> 1. A group of us agree to split the cost of the translation and we create
> any programming tools as required.
> 2. Each member of the group would need to submit a copy of their
> invoice/order for the LST as proof of legitimate ownership.
> 3. Word for word translation of the articles and tips in the LST
> magazine. This is the hardest and most costly part, because to the best
> of my knowledge, PCSoft do not supply the text electronically, so someone
> has to translate and type it out again in English. How frustrating and
> archaic. Maybe it could be scanned and OCR ?
> If PCsoft could be persuaded to supply the text electronically then the
> whole process would be much easier and their sales of the existing LST
> would surely improve.
> 4. We can use Windev to translate the code of each project into English
> 5. Code comments and statics with text - I am happy enough to use Google
> to translate these and paste them into the project myself - I have
> compared Google translations with an early copy of Systran Pro and Google
> is better - but others may prefer to have them fully translated.
> 6. I had already written a small program to produce a list of Hyper File
> field names used in a project and this could be used to produce a list for
> translation of the field names into English with accompanying captions.
> Using this list we could individually rename the field in the analysis for
> each LST project. Windev will re-write the code with the changed field
> names as part of the analysis change. The hyperfile field list program
> is on the WinDAsso site if anyone is interested in it.
> To get the English captions into the project we could manually enter them
> or we could do it dynamically by holding the file/field/caption
> information in a data base and use a global proc or class to re-write the
> caption prompts as the project executes
>
> This process will leave gaps in the projects that we would need to
> complete from our own endeavours but the combination of paid translation
> and our own efforts means that although as a group we would all pay for
> the translation of all the articles in each LST, we would only have to put
> further effort into those items that really were of interest.
> Possible issues:
> PCSoft's attitude to the idea. If there are enough interested forum
> members and we can come to an agreement on the process, then all we can do
> is ask PCSoft.
> How would we handle latecomers to the initial group, in terms of their
> financial contribution ? This whole process should be non-profit
> making.
> Where do we start - from which LST ?
> Do we translate the entire LST or have a vote on the articles.
> How do we communicate with each other - privately or via a sub forum to
> this forum ?
> Do we form a new group of interested members for each LST or do we commit
> to a set number of LST issues as a group ?
> How do we run the process, who handles the money ?
>
> I think there is value to be gained for us from the LST and PCSoft do not
> seem to have any interest in the translation, possible due to the
> cost/revenue ratio, so I hope my comments will provoke a discussion that
> will lead to a firm proposal and process to make best use of the LST for
> English speaking users.
>
> Regards
> Al
>
Message forwarded from pcsoft.us.windev