forked from Dolibarr/dolibarr
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix modules names consistency - French #525
Open
atm-thomasb
wants to merge
2,712
commits into
ATM-Consulting:develop
Choose a base branch
from
atm-thomasb:FIX_module_name_consistency
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix modules names consistency - French #525
atm-thomasb
wants to merge
2,712
commits into
ATM-Consulting:develop
from
atm-thomasb:FIX_module_name_consistency
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…#31268) * Use <= 0 instead of ! because delete method returns -1 or 1 * Added contact * Removed user from parameters
* fix phpstan * fix phpstan * fix phpstan * fix phpstan * fix phpstan
* Fix translation * Fix translation * Fix translation * Fix translation
* stars field for modulebuilder * Update commonobject.class.php --------- Co-authored-by: Laurent Destailleur <eldy@destailleur.fr>
* NEW retreive Thirdparty by account usefull for external link * Update api_thirdparties.class.php * Update api_thirdparties.class.php * Update api_thirdparties.class.php
* phpstan * phpstan
# Qual: Fix phan/stan notices in relation with UnknownObjectMethodCall Fix notices in classes with UnknownObjectMethodCall notices or classes related with these.
* Qual: Fix phan/phpstan notices # Qual: Fix phan/phpstan notices Fix several phan/phpstan notices * Fix spelling in Changelog
# Fix: ci phan notice is ok to be used for .
# Qual: Fix phan notices in dolgraph class This fixes most notices in the dolgraph class.
# Qual: Fix smtps.class Fix most phan notices in smtps.class
…arr#31395) * NEW: tables for product customer prices extrafields management * ADD: new tables in 21.0 migration
…r#31389) * llx_accounting_system: add missing fields during install The current code expects to be able to assign an author for the object and store the creation date. * Remove constraint The constraint is useless for the integrity of data of the table and for the business rules using this table, so we must avoid it if we can. This will avoid error when loading dump, errors on import and more... --------- Co-authored-by: Laurent Destailleur <eldy@destailleur.fr>
1) /home/alexandre/workspace/dolibarr/htdocs/societe/class/societe.class.php:1299 Attempt to read property "country_id" on null Triggered by: * BookKeepingTest::testBookKeepingCreate (6 times) /home/alexandre/workspace/dolibarr/test/phpunit/BookKeepingTest.php:53 * SocieteTest::testSocieteCreate (6 times) /home/alexandre/workspace/dolibarr/test/phpunit/SocieteTest.php:87 * SocieteTest::testSocieteFetch (6 times) /home/alexandre/workspace/dolibarr/test/phpunit/SocieteTest.php:114 * SocieteTest::testSocieteMerge (12 times) /home/alexandre/workspace/dolibarr/test/phpunit/SocieteTest.php:450 * SocieteTest::testSocieteUpdate (6 times) /home/alexandre/workspace/dolibarr/test/phpunit/SocieteTest.php:143
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: This PR only affects the french translation keys. The rest of this description is in french.
FIX|Fix issue#30964 modules names consistency
Cette PR a pour but d'unifiormiser le nommage des modules sur la page de configuration de Dolibarr et lorsque l'on clique sur la roue crantée pour configurer les-dits modules.
Ce renommage suit la logique suivante :
La page de configuration des modules suivra le modèle "Configuration du module XXXX"
EXEMPLE : "Pager de configuration" ou "Paramétrage" deviennent "Configuration du module"
Le nom du module doit être le même sur la page de Dolibarr et dans la configuration
EX : "Travaux Planifiés / Gestion des travaux programmés" devient "Travaux Planifiés" partout
---- En cas de conflits, le nom le plus complet/parlant est utilisé
EX : "Gestionnaire de Tickets" au lieu de "Ticket"
---- En cas de noms différents mais synonymes, le nom de module est privilégié
EX : "Gestion d'une Base de Connaissances" au lieu de "système de gestion des connaissances"
Lors d'une association de deux mots, la conjonction de coordination "et" est privilégié car majoritaire
EX : "Utilisateurs & Groupes" --> "Utilisateurs et Groupes"
EX : "Contrats/Abonnements" --> "Contrats et Abonnements"
L'utilisation de majuscules est normalisé à l'utilisation de majuscules pour chaque nom, car usage le plus répandu
EX : "Organisation d’événements" --> "Organisation d’Événements"
Quelques fautes d'orthographes ont été corrigées
EX : "congès" -> "congés", "paramétrages du" -> "paramétrage du"
Le pluriel est privilégié car prédominant et en cas de conflits
EX : "Base de Connaissance" --> "Base de Connaissances"
EX : "Imprimante Ticket" --> "Imprimantes Tickets"
Évidemment le sujet du nommage reste subjectif et à discussion.