Do you see a possibility to release a multilingual, or at least english
version of Lima VVA? Although i don't speak norwegian, i could do
translation work with the google translator.
Thanks for your effort & best reguards
Lukas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Translations are very much in my plans for Lima VVA, and I can indeed use some help. However, for me to accept your contributions, you must be willing to give up all rights to your work.
Last edit: Vidar Hasfjord 2021-02-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Vidar, I'm willing to give up any rights if you allow me to colaborate in translating this oustanding software to english or to spanish, or even portuguese.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am sorry that it has taken this long to get back to you about translation assistance, but I have now finally created a dedicated ticket for the (slow but) ongoing English translation I am currently working on. If you (or anyone else) want and are able to contribute, and you know the Norwegian language (or have a good AI/robot translator at hand), you can get started right away on the translation of the built-in help system (program documentation).
Sure, I'm in, but the Norwegian is somehow out of my knowledge, although
if google translate or bing or yandex can help I could try. Many thanks
for the mail.
Moderator: Snipped superfluous quoted content.
Last edit: Vidar Hasfjord 2021-02-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sure, I'm in, but the Norwegian is somehow out of my knowledge, although if google translate or bing or yandex can help I could try.
Unless you are familiar with source code, or very eager to get started, you may want to wait until I have a pre-release of my English version available that you can easily install and use as a base for further translation to other languages. I will try to accelerate my work on this, and hopefully publish an early version in the not too distant future.
On the other hand, if you are very eager to get started, and you are not afraid of source code, I have already added English translations to some resource files for the UI. The main menu and a few dialogs and message strings now have English translations. If you are brave, you can have a look at these resource files and provide Spanish/Portuguese translations.
See the commit log (code history) for the Euler branch. At the moment, the most recent translation change was committed in revision 1991, and I think the the first translation change was committed in revision 1923.
Thanks again!
Edit: Note that Lima VVA 5 (a.k.a. "Euler") moved to the trunk in [r2251], and the "euler" development branch hence no longer exists. Older releases can be found under "branches" and "tags".
Congratulations — you are now a member of the project!
You should now have permission to edit/update contents on this project site. I have created a wiki page [Glossary] for the terminology used in Lima VVA from the field of road design and earthwork calculation. You can start working on that page right away, by adding, defining and translating all the engineering terms used by Lima VVA.
For doing the actual work to add translations of the resources (menus, accelerators/shortcut keys, dialog boxes, message strings) within the software, Microsoft Visual Studio is used. A free Community Edition is available. Visual Studio has built-in resource editors that are fairly easy to use, and from my experience translating to English, seem to be sufficient for our purposes. So, if you want to help me do the actual implementation of another language, you will have to learn a little bit of Visual Studio, if you do not already know it. You also need to read up a little on Windows Resources and Resource File Format, so that you understand how shortcut keys are assigned within menus and dialog boxes, etc. And you need to learn how to access and commit changes to the Lima VVA source code (this project uses Subversion for source code version control).
However, if that is too much to ask, work on the Glossary alone would be helpful, and it is a great way to get started.
When I have finished the English translation of the help file, then you may be able to help there as well. That work does not need Visual Studio. You only need a text editor, preferably a HTML editor (Visual Studio has a powerful one built-in), as well as a basic understanding of hyperlinks. That said, I might shield you from the link details — a plain translation of the text would still be helpful.
Great to see you have already thrown yourself into the work!
However, you were not supposed to leave all my "blah blah blah"! You were supposed to replace them! I have cleaned it up now. :-)
There is a problem: We need to include all the abbreviations needed. I don't know Spanish, so I wouldn't know how to properly abbreviate words. So, I have edited the glossary to include abbreviations as well. For example, "alineamiento horizontal" is far too long to be used as a column header (needed in the report "Longitudinal section"). As an abbreviation, Lima VVA currently uses "h.align." in English and "h.kurv." in Norwegian. Please complete the Spanish translations with abbreviations. Abbreviations should be listed as alternative terms separated by vertical bar. For example, "horizontal alignment | h.align." in English, which translates to Norwegian as "horisontalkurvatur | h.kurv.".
Your Spanish translation for "kerb" is unclear: "cordón-cuneta/arcén". What does the slash mean? Don't use slash. Are these alternative terms? If so, separate alternative terms by vertical bar ("|"). And, if so, do you mean "cordón-cuneta | arcén" or "cordón-cuneta | cordón-arcén"? Likewise, your translation for "verge" is unclear: "margen/zona de protección".
Don't capitalise your translations unless the capitalisation has significance (e.g. for acronyms, such as "PVI", or German). Otherwise, use lower-case only. I have updated your entries so far.
Note that I use parentheses to include alternative terms not used by Lima VVA, each separated by vertical bar. For example, for the English term "median strip", the Norwegian translation is "midtrabatt (midtdeler | trafikkdeler)". The two Norwegian terms given in parentheses are not used by Lima VVA, but are widely used by Norwegian engineers, so they are useful to include (for search and comprehension).
Feel free to continue the good work on the [Glossary] by adding terms and completing definitions and translations. If anyone wants to help, let us know!
PS: I have now created a specific ticket for the Spanish translation, with you as the owner. Please use the ticket to document further work on the Spanish translation. See [tickets:#3]. General work on the [Glossary] should be discussed here.
I have made a new article on [Language_Support] in Lima VVA, and how to contribute. It includes guidance on how to use Visual Studio to edit the resource files for adding additional language support.
I've made progress with the Glossary. Sorry for the delay.
Great! Thanks for your contributions! And don't be sorry. Take your time. We are not on a schedule.
By the way, your annotations (explanations) need to be in English for me to understand them (although, with some help of Google Translate, I am able to make sense of it). If you want to, you can include Spanish annotations as well. E.g. put them in parentheses:
Elevation Spanish translation: "elevación | SNM". The term "elevación" is normally understood to be above sea level, or its most common use "SNM" ("Sobre el Nivel del Mar"). (Se entiende que es sobre el nivel del mar o su uso más común "SNM".)
PS. Feel free to add terms as well. You don't have to wait for me to add them. The list is far from complete.
Last edit: Vidar Hasfjord 2021-06-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Full English version is now available. Please check it out and let me know if you have any feedback (bug and omissions reports, corrections and suggestions for improvement).
If anyone wants to work on further translations (e.g. Chinese, French, German), you are welcome!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Vattila!
Do you see a possibility to release a multilingual, or at least english
version of Lima VVA? Although i don't speak norwegian, i could do
translation work with the google translator.
Thanks for your effort & best reguards
Lukas
Hi Lukas!
Thanks for getting in touch!
Translations are very much in my plans for Lima VVA, and I can indeed use some help. However, for me to accept your contributions, you must be willing to give up all rights to your work.
Last edit: Vidar Hasfjord 2021-02-28
Hi Vidar, I'm willing to give up any rights if you allow me to colaborate in translating this oustanding software to english or to spanish, or even portuguese.
Hi Lukas and Juan, are you still around?
I am sorry that it has taken this long to get back to you about translation assistance, but I have now finally created a dedicated ticket for the (slow but) ongoing English translation I am currently working on. If you (or anyone else) want and are able to contribute, and you know the Norwegian language (or have a good AI/robot translator at hand), you can get started right away on the translation of the built-in help system (program documentation).
See [tickets:#2].
PS. If you are unable to contribute, but still keen to see a translation, you can upvote the ticket to show your interest.
Related
Tickets: #2
Sure, I'm in, but the Norwegian is somehow out of my knowledge, although
if google translate or bing or yandex can help I could try. Many thanks
for the mail.
Moderator: Snipped superfluous quoted content.
Last edit: Vidar Hasfjord 2021-02-28
Hi Juan,
Unless you are familiar with source code, or very eager to get started, you may want to wait until I have a pre-release of my English version available that you can easily install and use as a base for further translation to other languages. I will try to accelerate my work on this, and hopefully publish an early version in the not too distant future.
On the other hand, if you are very eager to get started, and you are not afraid of source code, I have already added English translations to some resource files for the UI. The main menu and a few dialogs and message strings now have English translations. If you are brave, you can have a look at these resource files and provide Spanish/Portuguese translations.
See the commit log (code history) for the Euler branch. At the moment, the most recent translation change was committed in revision 1991, and I think the the first translation change was committed in revision 1923.
Thanks again!
Edit: Note that Lima VVA 5 (a.k.a. "Euler") moved to the trunk in [r2251], and the "euler" development branch hence no longer exists. Older releases can be found under "branches" and "tags".
Related
Commit: [r2251]
Last edit: Vidar Hasfjord 2023-06-14
Hi Juan,
A preliminary English version is now available. Please take a look!
See [tickets:#2] for details.
Great work, I'm looking for advice to where I must start for make the translation, or only for the resource files?
Last edit: Juan F. Domínguez 2021-03-15
Hi Juan,
Congratulations — you are now a member of the project!
You should now have permission to edit/update contents on this project site. I have created a wiki page [Glossary] for the terminology used in Lima VVA from the field of road design and earthwork calculation. You can start working on that page right away, by adding, defining and translating all the engineering terms used by Lima VVA.
For doing the actual work to add translations of the resources (menus, accelerators/shortcut keys, dialog boxes, message strings) within the software, Microsoft Visual Studio is used. A free Community Edition is available. Visual Studio has built-in resource editors that are fairly easy to use, and from my experience translating to English, seem to be sufficient for our purposes. So, if you want to help me do the actual implementation of another language, you will have to learn a little bit of Visual Studio, if you do not already know it. You also need to read up a little on Windows Resources and Resource File Format, so that you understand how shortcut keys are assigned within menus and dialog boxes, etc. And you need to learn how to access and commit changes to the Lima VVA source code (this project uses Subversion for source code version control).
However, if that is too much to ask, work on the Glossary alone would be helpful, and it is a great way to get started.
When I have finished the English translation of the help file, then you may be able to help there as well. That work does not need Visual Studio. You only need a text editor, preferably a HTML editor (Visual Studio has a powerful one built-in), as well as a basic understanding of hyperlinks. That said, I might shield you from the link details — a plain translation of the text would still be helpful.
Thanks again!
Related
Documentation: Glossary
Last edit: Vidar Hasfjord 2021-03-15
Hi Juan,
Great to see you have already thrown yourself into the work!
However, you were not supposed to leave all my "blah blah blah"! You were supposed to replace them! I have cleaned it up now. :-)
There is a problem: We need to include all the abbreviations needed. I don't know Spanish, so I wouldn't know how to properly abbreviate words. So, I have edited the glossary to include abbreviations as well. For example, "alineamiento horizontal" is far too long to be used as a column header (needed in the report "Longitudinal section"). As an abbreviation, Lima VVA currently uses "h.align." in English and "h.kurv." in Norwegian. Please complete the Spanish translations with abbreviations. Abbreviations should be listed as alternative terms separated by vertical bar. For example, "horizontal alignment | h.align." in English, which translates to Norwegian as "horisontalkurvatur | h.kurv.".
Your Spanish translation for "kerb" is unclear: "cordón-cuneta/arcén". What does the slash mean? Don't use slash. Are these alternative terms? If so, separate alternative terms by vertical bar ("|"). And, if so, do you mean "cordón-cuneta | arcén" or "cordón-cuneta | cordón-arcén"? Likewise, your translation for "verge" is unclear: "margen/zona de protección".
Don't capitalise your translations unless the capitalisation has significance (e.g. for acronyms, such as "PVI", or German). Otherwise, use lower-case only. I have updated your entries so far.
Note that I use parentheses to include alternative terms not used by Lima VVA, each separated by vertical bar. For example, for the English term "median strip", the Norwegian translation is "midtrabatt (midtdeler | trafikkdeler)". The two Norwegian terms given in parentheses are not used by Lima VVA, but are widely used by Norwegian engineers, so they are useful to include (for search and comprehension).
Feel free to continue the good work on the [Glossary] by adding terms and completing definitions and translations. If anyone wants to help, let us know!
PS: I have now created a specific ticket for the Spanish translation, with you as the owner. Please use the ticket to document further work on the Spanish translation. See [tickets:#3]. General work on the [Glossary] should be discussed here.
Related
Tickets: #3
Documentation: Glossary
Last edit: Vidar Hasfjord 2021-03-16
I have made a new article on [Language_Support] in Lima VVA, and how to contribute. It includes guidance on how to use Visual Studio to edit the resource files for adding additional language support.
Related
Documentation: Language_Support
I've made progress with the Glossary. Sorry for the delay.
Great! Thanks for your contributions! And don't be sorry. Take your time. We are not on a schedule.
By the way, your annotations (explanations) need to be in English for me to understand them (although, with some help of Google Translate, I am able to make sense of it). If you want to, you can include Spanish annotations as well. E.g. put them in parentheses:
PS. Feel free to add terms as well. You don't have to wait for me to add them. The list is far from complete.
Last edit: Vidar Hasfjord 2021-06-15
Full English version is now available. Please check it out and let me know if you have any feedback (bug and omissions reports, corrections and suggestions for improvement).
If anyone wants to work on further translations (e.g. Chinese, French, German), you are welcome!