-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌐 N°7932 Translations - British English #677
🌐 N°7932 Translations - British English #677
Conversation
82bcf68
to
8c254ca
Compare
8c254ca
to
f8587d2
Compare
f8587d2
to
d8a7d0c
Compare
@larhip You branched from |
@Hipska thanks for the hint! Thanks again for the hint :-) |
* This file is part of iTop. | ||
* | ||
* iTop is free software; you can redistribute it and/or modify | ||
* it under the terms of the GNU Affero General Public License as published by | ||
* the Free Software Foundation, either version 3 of the License, or | ||
* (at your option) any later version. | ||
* | ||
* iTop is distributed in the hope that it will be useful, | ||
* but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
* GNU Affero General Public License for more details. | ||
* | ||
* You should have received a copy of the GNU Affero General Public License | ||
* along with iTop. If not, see <http://www.gnu.org/licenses/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this part can be removed from each file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have created the translation with the support of a little script. This script copies the original English files and checks every file line by line.
From my point of view it would be a good idea to have the same content and line numbering in en an en_gb files, wouldn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm not sure, for example the EN GB
could have other @author
references than the EN US
versions, so line numbers will be hard to match anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's good to include only the copyright and license line. That said, it's not bad if files contain more information on licenses. I will apply the suggested modifications as they make sense.
datamodels/2.x/combodo-db-tools/dictionaries/en_gb.dict.combodo-db-tools.php
Outdated
Show resolved
Hide resolved
datamodels/2.x/combodo-db-tools/dictionaries/en_gb.dict.combodo-db-tools.php
Outdated
Show resolved
Hide resolved
Accepted in functional review, thanks for the contribution @larhip ! We'll see in technical review if some changes are needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost good regarding the copyright and license! Didn't check the actual translations yet, will do that at a later time.
Didn't realise there are so many inconsistencies in these dict files. But when starting from scratch for a new language, we should better get them all right and aligned from the start 😉
datamodels/2.x/authent-cas/dictionaries/en_gb.dict.authent-cas.php
Outdated
Show resolved
Hide resolved
datamodels/2.x/authent-external/dictionaries/en_gb.dict.authent-external.php
Outdated
Show resolved
Hide resolved
datamodels/2.x/itop-attachments/dictionaries/en_gb.dict.itop-attachments.php
Outdated
Show resolved
Hide resolved
datamodels/2.x/itop-oauth-client/dictionaries/en_gb.dict.itop-oauth-client.php
Outdated
Show resolved
Hide resolved
datamodels/2.x/itop-portal-base/dictionaries/en_gb.dict.itop-portal-base.php
Outdated
Show resolved
Hide resolved
dictionaries/ui/layouts/navigation-menu/en_gb.dictionary.itop.navigation-menu.php
Outdated
Show resolved
Hide resolved
dictionaries/ui/pages/errorpage/en_gb.dictionary.itop.errorpage.php
Outdated
Show resolved
Hide resolved
dictionaries/ui/pages/notifications-center/en_gb.dictionary.itop.notifications-center.php
Outdated
Show resolved
Hide resolved
dictionaries/ui/pages/oauth.landing/en_gb.dictionary.itop.oauth.landing.php
Outdated
Show resolved
Hide resolved
dictionaries/ui/pages/preferences/en_gb.dictionary.itop.preferences.php
Outdated
Show resolved
Hide resolved
// You should have received a copy of the GNU Affero General Public License | ||
// along with iTop. If not, see <http://www.gnu.org/licenses/> | ||
/** | ||
* @author Benjamin Planque <[email protected]> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did @BenGrenoble create this translation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. Its must be a copy past from another dict file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@larhip please fix 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For sure it is a copy of the English dictionary file :-)
As I wrote previously I did not create those translations all by hand but used a script which copies all en files an go through every line to check whether there is the need to change it in British English.
This makes it pretty easy for me to update all translations (I.e. with a new version of iTop).
As soon as I will change all those requested change by you @Hipska it will become a lot more work to create new translations with a new version.
In this case it would be great to have a feedback from the iTop maintainer which means Combodo. @BenGrenoble maybe you as PO could give us your opinion or make a decision between more or less “automated” British English translations and perfectly clean files (which is currently not the case for EN US)?
Don’t get me wrong: for me both is absolutely fine, but in case of preferring clean files (even if this is not the case for en.dict.*) there might be a higher risk that British English will be not that good maintained in case of new translations.
hope you got my point 😊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not worry for new translations (dict items) as you are stating, since Combodo maintainers run an automated tool to copy these new items to the other languages and marks them to be translating by adding ~~
suffix, so everybody knows its a dict item that still needs to be translated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right we will run an automated script on these dict.
For me it's ok if the names or the legal informations in the headers are not modified. As long as the format of the file is ok and the translation are good.
We've the history of the commit and @jf-cbd will double check while integrating the PR.
Accepted in technical review. I'll perform the necessary edits. |
Hey @jf-cbd , Since my fork is done in an organization (itomig-de/iTop instead of larhip/iTop) it is somehow impossible to allow you to modify this PR, we discussed that already in the past with Guillaume. It seems to be a restriction of GitHub. Thanks again! :-) |
Hey @larhip, thanks for the explanation :) |
@jf-cbd modifications merged :-) |
Base information
Symptom (bug) / Objective (enhancement)
New language files for British English
Checklist before requesting a review