Can you please tell me where the patches are, so I can bookmark it for the next round? The submission process is a bit tricky if you're not a regular coder on the project, and I already have 4 bookmarks to try to find my way around ;)
Our language style guide says to use (U+2026) and NOT ... This is even officially required for Microsoft translations into Scottish Gaelic. Please revert.
The MSDN article doesn't tell you to replace Unicode Ellipsis with 3 dots at all, but it explains when to avoid using ellipsis at all. This is meant for people designing the user interface though and not for translators - translators will translate what they are given and then follow the style guide for their own language. For example, Chinese/Japanese have a Unicode ellipsis character that's completely differnet from he one that Latin script is using.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for consufing you with the versions, I'll try to grab the translated file off the repository the next time.
And as to the Microsoft stuff, no, I can't link you to any documentation, because that documentation is not public and only available to localizers on the project. When we originally started translating for Microsoft, they wanted straight quotes and dot dot dot, so we still have that all over the place. Then when we started working on Windows 10, they suddenly required typographic quotes and unicode ellipsis. So, we have started migrating all our translations to the new style, but Microsoft isn't handing us any work orders to fix old strings.
So, Microsoft translations have inconsistent typography for historical reasons. So do some other projects that we haven't manage to update yet. That's no reason to force us to have inconsistent typography everywhere else too, especially when we update a translation. The NSIS file now has curly quotes and dot dot dot. Not good at all ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You say your changes are based on trunk but it does not look like that to me. Can you please respond on the tracker?
I took my last translation as I had it on my local hard disk and uploaded it to an unofficial Project that I created on Transifex. Then I grabbed the latest English version off trunk and updated the source on Transifex. Then I translated and updated everything according to current typographicsl conventions, terminology changes etc. Then I did my best to look at everything in WinMerge to make sure that I didn't mess up any duplicate if/else variables.
I probably messed up the header macros, since I never had that complete file - I copied the syntax off the German translation.
Does this answer your question? Is there anything that you still need from me?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is better if you start with the Scottish Gaelic we already have when updating. You even erased your own old credits in the .nlf file since you started fresh with English :) .
The English file is 7-bit ASCII clean and when you start adding fancy quotes and stuff you need to specify a codepage and the Scottish Gaelic in trunk already had it set correctly. When I see a patch come in that basically reverts to the old style I tend to get a bit confused since I'm no longer sure if it really is based on trunk etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why did you change the codepage to '-'? This language is not ASCII safe.
Why did you change the !insertmacro LANGFILE macro in the .nsh? It was already correct and you broke it.
Thank you.
I changed … (U+2026) to ... because that is what all the other language files are using and it is listed as correct on MSDN:
For future reference, patches should be submitted under patches, not bugs.
Can you please tell me where the patches are, so I can bookmark it for the next round? The submission process is a bit tricky if you're not a regular coder on the project, and I already have 4 bookmarks to try to find my way around ;)
Our language style guide says to use (U+2026) and NOT ... This is even officially required for Microsoft translations into Scottish Gaelic. Please revert.
The MSDN article doesn't tell you to replace Unicode Ellipsis with 3 dots at all, but it explains when to avoid using ellipsis at all. This is meant for people designing the user interface though and not for translators - translators will translate what they are given and then follow the style guide for their own language. For example, Chinese/Japanese have a Unicode ellipsis character that's completely differnet from he one that Latin script is using.
Patches: Click on Tickets here on the SF top bar and choose patches, not bugs. ( https://sourceforge.net/p/nsis/patches/ )
If you can link me to some Microsoft documentation that says to use U+2026 then I will revert.
If for example I use https://www.microsoft.com/en-us/language/Search I find:
Browse... Brabhsaich... Windows 8
Browse... Brabhsaich... Windows 10 Creators Update
&Browse... &Brabhsaich... Word 2017-QR2
Last edit: Anders 2017-12-18
Thanks for the info!
Sorry for consufing you with the versions, I'll try to grab the translated file off the repository the next time.
And as to the Microsoft stuff, no, I can't link you to any documentation, because that documentation is not public and only available to localizers on the project. When we originally started translating for Microsoft, they wanted straight quotes and dot dot dot, so we still have that all over the place. Then when we started working on Windows 10, they suddenly required typographic quotes and unicode ellipsis. So, we have started migrating all our translations to the new style, but Microsoft isn't handing us any work orders to fix old strings.
So, Microsoft translations have inconsistent typography for historical reasons. So do some other projects that we haven't manage to update yet. That's no reason to force us to have inconsistent typography everywhere else too, especially when we update a translation. The NSIS file now has curly quotes and dot dot dot. Not good at all ;)
I took my last translation as I had it on my local hard disk and uploaded it to an unofficial Project that I created on Transifex. Then I grabbed the latest English version off trunk and updated the source on Transifex. Then I translated and updated everything according to current typographicsl conventions, terminology changes etc. Then I did my best to look at everything in WinMerge to make sure that I didn't mess up any duplicate if/else variables.
I probably messed up the header macros, since I never had that complete file - I copied the syntax off the German translation.
Does this answer your question? Is there anything that you still need from me?
It is better if you start with the Scottish Gaelic we already have when updating. You even erased your own old credits in the .nlf file since you started fresh with English :) .
The English file is 7-bit ASCII clean and when you start adding fancy quotes and stuff you need to specify a codepage and the Scottish Gaelic in trunk already had it set correctly. When I see a patch come in that basically reverts to the old style I tend to get a bit confused since I'm no longer sure if it really is based on trunk etc.