SDK for Translators - PHPFusion 9: PHPFusion 9 Support - Official Home of the PHPFusion CMS

Home
Search

Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

Falk

asked 28 Dec 2015 at 05:40 PM

Super Admin

If you master Github you can make requests directly to the directory here : https://github.com/PHPFusion/PHPFusion-9-Locale

If you want other methods, please simply attach the files to this thread or mail them to us. ( management@php-fusion.co.uk )

Flags as seen in the English locale folder can be found in images/flags and images/small_flag

Copy your large flag from images/flags to locale/YourLanguage/Language.png
Copy your small flag from images/small_flag to locale/YourLanguage/Language-s.png

To make it as simple and structured as possible I recommend that you have a clean folder structure on your translations working space.

Like :

\locale\YourLanguage\
\infusions\forum\locale\YourLanguage\
\infusions\articles\locale\YourLanguage\
\infusions\blog\locale\YourLanguage\
\infusions\downloads\locale\YourLanguage\
\infusions\faq\locale\YourLanguage\
\infusions\forum\locale\YourLanguage\
\infusions\gallery\locale\YourLanguage\
\infusions\member_poll_panel\locale\YourLanguage\
\infusions\news\locale\YourLanguage\
\infusions\rss_feeds_panel\locale\YourLanguage\
\infusions\shoutbox_panel\locale\
\infusions\weblinks\locale\YourLanguage\
\includes\jscripts\tinymce\langs\
\themes\Septenary\locale\
readme-en.html

etc.

I have attached translate_structure_sdk.zip that follows the correct structure.
Pay special attention to shoutbox_panel and rss_feeds_panel, the locale file is not in a folder but in the root of the directory.

Always use English locale as base locale from the main download pack, it is guaranteed to be updated.
Copy the files from the English directories to match the SDK structure.
Make sure that you save the files in UTF-8 Without BOM.

Once your translation is done Git it or zip the whole folder structure and attach or send it to us and we will include it for you.

Also a reminder, Please do not translate any object names anywhere.

Chan Wrote :

Quote

Hi guys, please note that these terms should not be translated and to be left as english.

"Infusions"
"Defender"
"Dynamics"
"PHPFusion"
"Quantum Fields"
"TinyMCE"

I notice Malay called Infusion as Infusi. That's not correct. Infusion is an object name, and a patented term by PHPFusion to refer as its system module.

- Same goes as TinyMCE, please don't go translate them as "SmallMCE" or "Small Editor", etc
- Same goes as Dynamics, please don't go translate them as "Transforming Fields" or "Transformer" or "Fast Transform" , etc
- Same goes with PHPFusion, don't go translate them as "PHP-Merge", etc.
- Same goes with Defender, don't go translate them as "Defense" or "Shield".
- Don't go translate CSS, HTML, or LESS, or SASS. I have seen LESS referred to "not more" in stack-overflow
- Same goes with referring to Quantum, don't go translate them "automatic field creator engine". You can however translate User Fields as Member Fields in any language.

Edited by N/A on 24-04-2017 18:21, 7 y

Falk attached the following file:

translate_structure_sdk.zip [No information available / 785 Downloads]

0 replies

Not to mention that we already have problems with numbers in translation. Example:
English:

Quote

There are currently %s pending for your review

Lithuanian (without utf-8 now to make it readable):

Quote

Siuo metu yra %s pateikimai, laukiantys patvirtinimo

Problem with "pateikimai" is that it can be used only when there is more than 1 submission but less than 10. This is why Lithuanian is hard. In order to have fully official language we should do that:
1 (submission) - pateikimas
2-9 - pateikimai
10 and more - pateikimu

0 replies

Falk

answered 19 Jan 2016 at 09:52 AM

Super Admin

I know there was some discussions about that issue for other languages as well, I will ask Hien if it was tackled with some solution.

Is 0 submissions also same as - pateikimas ?

0 replies

No, it should say "pateikimu"* - as no submissions.

pateikimų - with utf-8.

0 replies

I don't want to sound mean, but how you managed translations during the update of code is really bad. At first all translations were updated at the same time (like if you mane changes to English, you make changes to all other languages). But right now I have to check and compare each and every file of translations to see if anything is changed: are there new variables, are their names changed, are there changes in text.

In the future if you do some translation updates, please do same updates in all the translations so we don't have to recheck every line of code and look for changes.

Peace :G

0 replies

Hi,
I suggest to create a gist file or a file within the repository where we track changes to locale files. Because if I change something I can not translate everything in all languages.

The only thing I could do is add a variable and leave it English until someone will translate it.

Best,
SuN

Edited by SuNflOw on 19-01-2016 23:03, 8 y

0 replies

Adding a variable in English is ok. We can see what changes were made the github itself, like it shows the last change, it shows history. Just when adding new variable, write a comment to it like "// translate this" and it would enough. Because is you edit only english locale, then it is hard to keep up, as it cat be simple corrections in locale itself (without dependency on other locales) or ir can be whole-locale field correction.

Edited by N/A on 19-01-2016 22:42, 8 y

0 replies

Falk

answered 19 Jan 2016 at 09:10 PM

Super Admin

I totally agree.
The normal procedure is that we have a file or a forum thread that lists version changes in respective locale file.
To ask for a dev to update up to 30+ separate translations is just not viable. That will certainly only work as a bottle neck for devs since they will think both once and twice before doing anything in such scenario.

What happened here was a that quite a few Translators started to translate the beta, long before we flagged OK to translate. It was not viable for us to keep up with all locale changes in the translations at that time, we wanted to focus on the release.

I know that I mentioned that it was a tad early to translate but still fun to see people go at it, however it is better to wait to the RC since a lot of changes were in the pipeline. But it hard to follow all discussions for sure.

Great work on the patching tho ;)

Edit, for clarification. For any future revisions I will do the best to track locale changes for translators.

Edited by N/A on 19-01-2016 22:46, 8 y

0 replies

There's a spelling mistake in the English locale in setup.php
$locale['setup_1018'] = "You can exit this installer right now by clicking the button below. This will rename yoru config_temp.php file back to config.php.";
It should be:
$locale['setup_1018'] = "You can exit this installer right now by clicking the button below. This will rename your config_temp.php file back to config.php.";

0 replies

Falk

answered 22 Jan 2016 at 09:03 AM

Super Admin

Thank you.

0 replies

There's another mispelling in locale/permalinks/faq.php
$locale['pl_faq_cat_title'] = "FaQ´s";
It should be with capital letters
$locale['pl_faq_cat_title'] = "FAQ´s";
Also
$locale['pl_faq_cat_desc'] = "Enable FaQ Category Permalink on the Site.";
to
$locale['pl_faq_cat_desc'] = "Enable FAQ Category Permalink on the Site.";

0 replies

Falk

answered 1 Feb 2016 at 09:27 AM

Super Admin

Thank you for taking notice, I do think it is more of a typographic question, some want FAQ other want Faq and a few want FaQ, ive seen it all, right or wrong. Naturally, our spelling of it need to be consistent.

0 replies

I've taken notice because in all the other files FAQ is written in capital letters, so I assumed that this is the standard and I think that we should pay attention to every tiny detail because this CMS is a premuim CMS. That's my point :).

Edited by ctokepa on 08-02-2016 00:55, 8 y

0 replies

Falk

answered 2 Feb 2016 at 09:01 AM

Super Admin

Good thinking and exactly my point :)
Change will be made to it for consistency, thank you.

0 replies

In admin\settings.php there's another standard mismatch
$locale['eshop_settings'] It is written Eshop instead of eShop.

0 replies

Falk

answered 8 Feb 2016 at 09:18 AM

Super Admin

Thank you , ;)

0 replies

— 1 month later —

The translation to Bulgarian goes slowly because of the lack of a spare time but I've found a new mistake in locale\admin\English\migrate.php
$locale['101'] = "You must select two differant users for migration";
Should be
$locale['101'] = "You must select two different users for migration";
Soon I will post the whole translation. Sorry for the delay!

Edited by ctokepa on 19-03-2016 23:24, 8 y

0 replies

Falk

answered 20 Mar 2016 at 09:24 AM

Super Admin

No worries, take your time :) fixed the spelling. Thank you !

0 replies

Another mistake:
$locale['download_0204'] = "Downloads Source: Please either provide a Downloads file or a Uri
to
$locale['download_0204'] = "Downloads Source: Please either provide a Downloads file or a URL
:)

0 replies

Falk

answered 25 Mar 2016 at 11:58 PM

Super Admin

0 replies

Another mistake:
forum\locale\English\forum.php
$locale['forum_0225'] = "[bcolor=#ff0000]Sortby[/bcolor]";
to
$locale['forum_0225'] = "[bcolor=#ff0000]Sort by[/bcolor]";

0 replies

Category Forum

Locales Forum - 9

Labels

None yet

Statistics

Views 0 views
Posts 53 posts
Votes 0 votes
Topic users 15 members

15 participants

Notifications

Track thread

You are not receiving notifications from this thread.

SDK for Translators - PHPFusion 9

53 posts

PHPFusion

Resources

Community

Development