translation, very partial

[ChurchCRMBugReport]

Hi, I've installed (locally, on my ubuntu laptop) churchCRM, and everything is working well, except translation.

I've defined my language in churchcrm > admin > Edit general settings > Localization > sLanguage > French - France [fr_FR] Most (99%) of the interface is still in english, there is only a few french sometimes (I think only a few javascript things are translated)

Any help or suggestion welcomed...

Collected Value Title	Data
Page Name	/churchcrm/SystemSettings.php
Screen Size	768x1366
Window Size	623x1366
Page Size	888x1596
Platform Information	Linux churchcrm 4.15.0-62-generic #69-Ubuntu SMP Wed Sep 4 20:55:53 UTC 2019 x86_64
PHP Version	7.2.19-0ubuntu0.18.04.2
SQL Version	5.5.5-10.1.41-MariaDB-0ubuntu0.18.04.1
ChurchCRM Version	3.4.0
Reporting Browser	Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Prerequisite Status	All Prerequisites met
Integrity check status	{"status":"success"}
Apache Modules	core,mod_so,mod_watchdog,http_core,mod_log_config,mod_logio,mod_version,mod_unixd,mod_access_compat,mod_alias,mod_auth_basic,mod_authn_core,mod_authn_file,mod_authz_core,mod_authz_host,mod_authz_user,mod_autoindex,mod_deflate,mod_dir,mod_env,mod_filter,mod_mime,prefork,mod_negotiation,mod_php7,mod_reqtimeout,mod_rewrite,mod_setenvif,mod_status

[DawoudIO]

please see - https://github.com/ChurchCRM/CRM/wiki/System-locale

[PaulPoulain]

yikes... I think I must have checked the locale in my main console, not in the churchcrm lxc container... locale set, apache restarted, problem fixed. Thanks @DawoudIO

Note: it requires systemctl apache2 restart + the link to the howto is not working anymore. If you give me wiki change access, I can fix that (and promize that I won't harm anything. Look at my github bio to get more info about who I am. the churchCRM involvement is private, not linked to BibLibre)

[crossan007]

@PaulPoulain I've added you to the Documentation group in our team. Thanks for offering to improve the documentation.

[Florian-git]

@PaulPoulain If you plan to use ChurchCRM in french, I think we should try to work together. I've already improved french translation in POEditor (from 93% to 99,xx%) There are still some bugs:

• Most PDF or flat files generated don't display accented characters but a code (ex: 1ère année: au lieu de 1ère année)
• Some fields are not translated. (it's an issue in .php files cc @DawoudIO Example : "See All People" in phpfile instead of "See all People" in messages.po)
• Fields size in PDF generated seems to be fixed, fitted to english text, resulting in overlapped characters.
• Menus items are too long in french, resulting in unreadable items (exemple : 'Afficher les familles actives' et 'Afficher les familles inactives' displaying the same text "Afficher les familles ...")

[PaulPoulain]

Hello @Florian-git , Working together is a good proposal I'm happy to welcome. How to communicate ? Should we have an issue "translation to french" [where we could communicate in French] ? by email ? (mine : paul.poulain at free.fr, the personal one, the one on my github profile is the business one, and I try to separate business / personal activities) about "Afficher les familles", quelques suggestions :

• utiliser "Voir" au lieu de "Afficher"
• ne pas mettre le "les" ce qui donnerait => "Voir familles actives". Il faudrait faire ce genre de choses un peu partout si on veut une traduction cohérente. Donc à bien réfléchir...

[crossan007]

How to communicate

I suggest using the Issue tracker on this GitHub repository for the majority of your communication (especially if it pertains to a specific issue or something that needs to be changed in the code). That way other project users can see the progress.

We like to see one "GitHub Issue" per actual issue. I.e. each of the items listed by @Florian-git should have a unique issue number so we can discuss that particular problem. This may even be as granular as opening an issue when you notice a single missing phrase; don't worry about creating "too small" issues.

[PaulPoulain]

OK for using github, but if we open many french-related issues, we need a way to group them under an umbrella. Could we have a project 'translation to french' ? I agree with the 1topic = 1 issue. But we also have some general strategy questions to solve. Like "how to translate 'Show'". 'Voir', 'Afficher' are both acceptable in French. The 1st being shorter, the 2nd being better imho. But if we decide to go for 'voir' we need to change it everywhere in churchCRM.

[crossan007]

I think there are two(or more?) classifications for communication here:

1) Issues with the application, or the strings it's trying to translate. All 4 of @Florian-git's points fit into this category, as each will need a code change. Additionally, string in the software not included for translation fit this category as well. All issues in this category should certainly be GitHub issues.

2) Language-specific translation nuances (Voir vs Afficher). I hadn't considered this when I made my comment above, so I do question the benefit of using GitHub for these types of discussions; however, I think that POEditor.com supports discussions around a string, so that may be your best option here:

Again, thanks for all the thought and effort you're putting into this.