Open joyfullservice opened 4 years ago
@Indigo744, @effjot, @cenx1, @kocivan - Let me know if you have any thoughts on the localization idea... 😄 Ideas are welcome!
Thank you for pinging me.
While I'm French, and my Office is in French, I'm more in favour of the first (neat, but not really necessary). Devs are familiar with English, and this extension requires a fair amount of technical knowledge since it is tied to a VCS.
That said, if you want to go this route, I'll be happy to help and provide the French translation 😸
I’m more in camp #1, too. Is there already a i18n framework for VBA (most programming languages do, but VBA isn’t like most programming languages…), or would it have to be written from scratch? (Looking at gettext, this could end up quite complicated. PO files and the gettext framework have a lot of functions to cater to the nooks and crannies that each language seems to bring with it.)
Should i18n happen some time in the future, I could help with a German translation.
Number 2 - I would like to participate and contribute with translations. Would be a text file or an xml file?
Number 2 - I would like to participate and contribute with translations. Would be a text file or an xml file?
Thank you for your interest in contributing! My plan on this was to use .po files, which seems to be a standard way to integrate translations into software programs. Internally, the add-in would store the strings in a table, but would export and import to .po files, which could be easily edited in programs like Poedit or even a text editor. The .po files would be maintained in version control in this project, and contributions would be made through standard pull requests on GitHub.
I am planning to write a module to handle the translation functions, and this would handle the integration with the .po files as well as maintaining the internal table of translation strings. While many systems would parse the source code to build the strings, I am planning to take a simpler approach and have the T()
function verify that the string exists, and add it automatically if it doesn't. This will generate the strings automatically during the usage of the program and then allow them to be exported to .po files for the actual translation work.
This project is really amazing. Congratulations.
Any good news about this feature?
I actually made some progress on this earlier today. It's not quite ready to start translating strings yet, but getting closer! Hopefully I can fit in a few hours on this over the next couple weeks to finish the basic implementation, then you will be able to do the actual translation of the text strings. 😄
Thank you for your feedback. I'm very excited to start.
On Sat, 15 May 2021 at 23:45, Adam Waller @.***> wrote:
I actually made some progress on this earlier today. It's not quite ready to start translating strings yet, but getting closer! Hopefully I can fit in a few hours on this over the next couple weeks to finish the basic implementation, then you will be able to do the actual translation of the text strings. 😄
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/joyfullservice/msaccess-vcs-integration/issues/87#issuecomment-841757086, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATQRUQ6RPTMKGELQJGF32E3TN4WTTANCNFSM4TSIKIUA .
-- Atenciosamente Juliano Santos Lima (+55) 27 9 9761-8946 - Cel/Mobile (+55) 27 9 9747-4634 - Cel/Mobile (+55) 27 3761-1263 - Casa/Home "Nenhuma grande descoberta foi feita jamais sem um palpite ousado." "Loucura é fazer tudo sempre do mesmo jeito esperando resultados diferentes" "Coming together is a beginning. Keeping together is progress. Working together is success."
@petrukio - I have created a first draft of a translation file. Would you be able to open it up in something like Poedit and create a .po
translation file for me? That will help me to have some translated strings that I can use for testing the loading and display of translated content. Of course there will be many more strings added as this is implemented, but this will give us most of the strings shown in the user interface.
After creating the .po
translation file, please upload it in a comment here, and I will use that for further testing as I continue to develop this functionality. Thank you for your help!
Sure, no problem. Find attached By the way, one sentence is incomplete: The build functionality in this tool is fairly new with limited testing in real-world applications. It is very important that you test this carefully in your environment to make sure everything you need is being created in your database duri
I translated it to brazilian portuguese but I guess would be good if you complete the sentence.
On Wed, 19 May 2021 at 22:02, Adam Waller @.***> wrote:
@petrukio https://github.com/petrukio - I have created a first draft of a translation file. Would you be able to open it up in something like Poedit https://poedit.net/ and create a .po translation file for me? That will help me to have some translated strings that I can use for testing the loading and display of translated content. Of course there will be many more strings added as this is implemented, but this will give us most of the strings shown in the user interface.
MSAccessVCS.zip https://github.com/joyfullservice/msaccess-vcs-integration/files/6512187/MSAccessVCS.zip
After creating the .po translation file, please upload it in a comment here, and I will use that for further testing as I continue to develop this functionality. Thank you for your help!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/joyfullservice/msaccess-vcs-integration/issues/87#issuecomment-844601700, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATQRUQ6IF4YJT5SOU5YMBA3TORNRRANCNFSM4TSIKIUA .
-- Atenciosamente Juliano Santos Lima (+55) 27 9 9761-8946 - Cel/Mobile (+55) 27 9 9747-4634 - Cel/Mobile (+55) 27 3761-1263 - Casa/Home "Nenhuma grande descoberta foi feita jamais sem um palpite ousado." "Loucura é fazer tudo sempre do mesmo jeito esperando resultados diferentes" "Coming together is a beginning. Keeping together is progress. Working together is success."
@petrukio - Thank you! But for some reason I don't see any file attached... You might have to put it in a zip file to attach it to your comment.
Also, here is the rest of that string:
PLEASE NOTE: The build functionality in this tool is fairly new with limited testing in real-world applications. It is very important that you test this carefully in your environment to make sure everything you need is being created in your database during the build.
Please see the online documentation for additional details on the build process. If you encounter an issue, please feel free to submit issues and/or pull requests on the GitHub project.
PLEASE NOTE The build functionality in this tool is fairly new with limited testing in real-world applications. It is very important that you test this carefully in your environment to make sure everything you need is being created in your database during the build. Please see the online documentation for additional details on the build process. If you encounter an issue, please feel free to submit issues and/or pull requests on the GitHub project.
TOME NOTA: A funcionalidade de geração nesta ferramenta é bem recente com limitações a testes em aplicações reais. É muito importante que você faça testes com cuidado em seu ambiente para garantir que tudo que voce precisa esteja sendo criado em seu banco de dados Por favor verifique a documentação online para detalhes adicionais no processo de construção. Se caso encontrar algum problema, fique à vontade para submeter pendências e/ou Pull requests no projeto do GitHub
Thank you!! Could you also attach the file with the rest of the translations? I am not seeing it here...
@petrukio - I think you might have to attach it on the GitHub web page, not just in the email. I think the email attachments get taken out when you reply by email. If you visit this page: https://github.com/joyfullservice/msaccess-vcs-integration/issues/87 you can attach the file to a comment. Thanks!
I know several of you are using this add-in on systems that use other languages and locales. I would be interested in some feedback about potentially adding some translation/localization features to this add-in so that the UI and log file entries are displayed in your preferred language.
On the back end, we would simply wrap text strings in a
T("My English text")
function, and probably maintain a local table in the add-in with the translations. (These could be imported/exported from a .po file if that is easier to manage/edit.)What do you think? I could see a few potential perspectives on this:
If there is enough interest, I wouldn't mind helping put the basic framework together for this.