joomla / core-translations Goto Github PK

Steps to reproduce the issue

install Joomla 4 and use English USA as the default language

create a new article on frontend or backend

note the tab

Expected result

Actual result

System information (as much as possible)

Additional comments

Hi, the workflow: core-get-language-source-v4.yml is beeing executed on forks which fails cause no data are beeing attached. So please make sure its only triggered for the main repo :)

Btw it only claims that i triggered something for unknown reason. I might have updated the branch to the newest version but i have not manually triggered anything like that.

At Joomla forum https://forum.joomla.org/viewtopic.php?f=809&t=1002325 it was reported that

joomla wants to constantly update Bulgarian language and as I update it the message appears again.

I've checked the update site https://update.joomla.org/language/details4/bg-BG_details.xml
It cmmunicates that bg-BG language is 4.2.8.2

I've downloaded that bg-BG_joomla_lang_full_4.2.8v2.zip language pack.
The manifest file pkg_bg-BG.xml wrongly states: 4.2.8.1

Steps to reproduce the issue

1. Installation language ps-AF (Pashto Afghanistan).
2. activate content language ps-AF
3. set ps-AF as default administrator language.

Expected result

Language work.

Actual result

System Error Page: Fatal error: Cannot declare class En_GBLocalise, because the name is already in use in /mnt/data/vhosts/casite-1461580.cloudaccess.net/httpdocs/administrator/language/ps-AF/localise.php on line 23

System information (as much as possible)

Additional comments

Reported at joomla/joomla-cms#42511.

Installation Blog sample data fails (Hungarian, Thai)

Data too long for column 'menutype' at row 1

Source string: PLG_SAMPLEDATA_BLOG_SAMPLEDATA_MENUS_ITEM_3_TITLE

@conconnl
As I don't know where to post this, here is one of my findings on Crowdin:

This confuses Pashto tag ps-AF with Afrikaans => tag af-ZA,
Dari Persian tag prs-AF for which we had a pack in J3 is absent from the list.

Originally posted by @infograf768 in #54 (comment)

1. The manifest does not contain the updateserver

<updateservers>
		<server type="collection" priority="1" name="Accredited Joomla! Translations"/>
	</updateservers>

2. The jalali date is no more present because of missing code in localise.php and missing installing the calendar js in media.

----Missing code
A. in site install.xml missing

    <files>
		<folder>/</folder>
        <filename file="meta">install.xml</filename>
      </files>

	<media destination="fa-IR">
	    <filename>index.html</filename>
		<filename>js/index.html</filename>
		<filename>js/calendar-setup.js</filename>
		<filename>js/calendar.js</filename>
        <filename>js/calendar-setup-uncompressed.js</filename>
		<filename>js/calendar-uncompressed.js</filename>
	</media>

files which are present in the js folder

B. in localise.php missing the whole class fa_IRDate extends JDate {

Steps to reproduce the issue

1. Install English (Canada) language pack.
2. Enable as a content language.
3. Create a category and set language to English (Canada)
4. Save.
5. Jooomla error screen appears.

Expected result

should be able to save the Category.

Actual result

Joomla Error screen appears.

System information (as much as possible)

see additional comments

Additional comments

/** * en-CA localise class. * * @SInCE 1.6 /abstract class En_GBLocalise{ /* * Returns the potential suffixes for a specific number of items * * @param integer $count The number of items.

Please add Sinhala Language pack to Joomla 4 and 5

The following was reported in the Joomla forum de: the version information is missing in the XML file in the Arabic language package. That's why it keeps asking for an update even though the current version has already been installed.

I sent this page to the user : https://volunteers.joomla.org/teams
https://volunteers.joomla.org/joomlers/564-private-profile-375901e3
regards
Christine

Is your feature request related to a problem? Please describe.

Marathi is a language spoken by 83 million people in India. Joomla v4 doesn't have support for this language.

Describe the solution you'd like

Please create setup for Marathi so that we can contribute translating Joomla CMS. Adding another willing contributor: @abhidesh128

Additional context

Hi:

Where can people download Galician translation, please?

It's not available here: https://downloads.joomla.org/es/language-packs/translations-joomla4

But it's available to translate in Crowdin.

Thank you and best regards

I saw that there used to be a Scottish Gaelic Language Pack for Joomla! 2.5.7.1 (eons ago). It is at Joomla! 2.5 - Scottish Gaelic.

I'd love to get this going with 4.x. I don't know Scottish Gaelic sadly but happy to try to do the legwork and get help from Scot friends if someone would point me at 'how to update an old language pack' or similar doc. I've done localisation projects before for European languages so Im familiar with the concepts.

Or indeed happy to help if someone is doing this?

Issue Description

Language: Sinhala
Native name: සිංහල
Code: si
Crowdin ID: @helabasa
Current Status: Joomla CMS 3 Translator & Proofreader
Problem: We don't have proofreader right/permission on new enterprise platform

Projects list

1. Joomla CMS
2. Joomla Official Extensions
3. Joomla Official Template
4. Joomla Official Website

Also, can you enable sinhala language for below projects and apply same permission?

1. Easyblog
2. Easysocial
3. Easyarticles
4. Easydiscuss
5. Payplans
6. Komento
7. Yoursites
8. Opening hours module
9. RSForm
10. RStickets
11. RSmail
12. RSfiles
13. RSdirectory
14. RSmembership
15. RSfirewall
16. RSfeedback
17. RSevents
18. RSblog
19. Conversekit
20. RSseo
21. RSmediagallery
22. RScomments
23. Shika
24. Jbolo
25. Zero-24
26. Joomla marketing resources

Latest uk-UA language pack is missing pkg_uk-UA.xml witch is causing rsync synchronisation error https://github.com/joomla/core-translations/actions/workflows/remote-get-ukrainian.yml

Installation of Blog Sample Data using Dutch language fails at step 1:

Reason is using tag "Houden van" 2 times:

PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_0_TITLE="Miljoenen"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_1_TITLE="Houden van"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_2_TITLE="Houden van"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_3_TITLE="Joomla 5"

To provide context / comments to translators language strings need to be extended with additional information.
Example:

JHELP_EXTENSIONS_MODULE_MANAGER_ADMIN_LATESTACTIONS="Admin_Modules:_Action_Logs_-_Latest" ; Translate only if you have your own documentation server

Posting this here rather than DM'ing on glip just because it might be useful for others.

I can see a com_csp file for Farsi language. This file has been removed from core for nearly a month. So given the sync from crowdin has been relatively recent how does it still end up in this repo? I presume this is how the sync with crowdin is performed or similar?

ref: https://github.com/joomla/core-translations/blob/main/joomla_v4/translations/package/fa-IR/administrator/language/fa-IR/com_csp.ini

The com_finder.commonwords.txt is a special file.
The words are unique per language and don't have the same amount.
The normal processing structure for TXT doesn't work for this file

As title say, create a new workflow for the joomla 5 translations maybe based on the crowdin branch feature.

https://support.crowdin.com/versions-management/

Hi,
I've just noticed that the langmetadata.xml files for Hungarian translation contains incorrect entries between tags and .

This is the current - incorrect - state:

<firstDay>0</firstDay>
<weekEnd>0,6</weekEnd>

And this should be the correct one IMHO:

<firstDay>1</firstDay>
<weekEnd>6,7</weekEnd>

Because of the wrong entries, calendars will show non-native ordering of week days.

What am I supposed to do? Create a pr, or something else? I've seen some comments regarding that langmetadata.xml is handled inside Crowdin, but I'm not sure what this actually means in this case.

After I read joomla/joomla-cms#38509 I did a quick grep of current main branch of this repository using grep -rl --include \*.php 'En_GBLocalise' Below is the result:

ar-AA/administrator/language/ar-AA/localise.php
ar-AA/language/ar-AA/localise.php
az-AZ/administrator/language/az-AZ/localise.php
az-AZ/language/az-AZ/localise.php
bg-BG/administrator/language/bg-BG/localise.php
bg-BG/language/bg-BG/localise.php
bn-BD/administrator/language/bn-BD/localise.php
bn-BD/language/bn-BD/localise.php
bs-BA/administrator/language/bs-BA/localise.php
bs-BA/language/bs-BA/localise.php
ca-ES/administrator/language/ca-ES/localise.php
ca-ES/language/ca-ES/localise.php
en-AU/administrator/language/en-AU/localise.php
en-AU/language/en-AU/localise.php
en-CA/administrator/language/en-CA/localise.php
en-CA/language/en-CA/localise.php
en-NZ/administrator/language/en-NZ/localise.php
en-NZ/language/en-NZ/localise.php
en-US/administrator/language/en-US/localise.php
en-US/language/en-US/localise.php
en-ZA/administrator/language/en-ZA/localise.php
en-ZA/language/en-ZA/localise.php
eo-XX/administrator/language/eo-XX/localise.php
eo-XX/language/eo-XX/localise.php
et-EE/administrator/language/et-EE/localise.php
et-EE/language/et-EE/localise.php
eu-ES/administrator/language/eu-ES/localise.php
eu-ES/language/eu-ES/localise.php
fa-AF/administrator/language/fa-AF/localise.php
fa-AF/language/fa-AF/localise.php
fa-IR/administrator/language/fa-IR/localise.php
fa-IR/language/fa-IR/localise.php
fi-FI/administrator/language/fi-FI/localise.php
fi-FI/language/fi-FI/localise.php
fit-FI/administrator/language/fit-FI/localise.php
fit-FI/language/fit-FI/localise.php
ga-IE/administrator/language/ga-IE/localise.php
ga-IE/language/ga-IE/localise.php
gl-ES/administrator/language/gl-ES/localise.php
gl-ES/language/gl-ES/localise.php
gu-IN/administrator/language/gu-IN/localise.php
gu-IN/language/gu-IN/localise.php
he-IL/administrator/language/he-IL/localise.php
he-IL/language/he-IL/localise.php
hi-IN/administrator/language/hi-IN/localise.php
hi-IN/language/hi-IN/localise.php
hr-HR/administrator/language/hr-HR/localise.php
hr-HR/language/hr-HR/localise.php
hu-HU/administrator/language/hu-HU/localise.php
hu-HU/language/hu-HU/localise.php
hy-AM/administrator/language/hy-AM/localise.php
hy-AM/language/hy-AM/localise.php
id-ID/administrator/language/id-ID/localise.php
id-ID/language/id-ID/localise.php
it-IT/language/it-IT/localise.php
ka-GE/administrator/language/ka-GE/localise.php
ka-GE/language/ka-GE/localise.php
kk-KZ/language/kk-KZ/localise.php
km-KH/administrator/language/km-KH/localise.php
km-KH/language/km-KH/localise.php
ko-KR/administrator/language/ko-KR/localise.php
ko-KR/language/ko-KR/localise.php
ky-KG/administrator/language/ky-KG/localise.php
ky-KG/language/ky-KG/localise.php
lo-LA/administrator/language/lo-LA/localise.php
lo-LA/language/lo-LA/localise.php
lt-LT/administrator/language/lt-LT/localise.php
lt-LT/language/lt-LT/localise.php
lv-LV/administrator/language/lv-LV/localise.php
lv-LV/language/lv-LV/localise.php
mk-MK/administrator/language/mk-MK/localise.php
mk-MK/language/mk-MK/localise.php
ml-IN/administrator/language/ml-IN/localise.php
ml-IN/language/ml-IN/localise.php
mn-MN/administrator/language/mn-MN/localise.php
mn-MN/language/mn-MN/localise.php
mr-IN/administrator/language/mr-IN/localise.php
mr-IN/language/mr-IN/localise.php
ms-MY/administrator/language/ms-MY/localise.php
ms-MY/language/ms-MY/localise.php
nb-NO/administrator/language/nb-NO/localise.php
nb-NO/language/nb-NO/localise.php
ng-NA/administrator/language/ng-NA/localise.php
ng-NA/language/ng-NA/localise.php
nn-NO/administrator/language/nn-NO/localise.php
nn-NO/language/nn-NO/localise.php
oc-FR/administrator/language/oc-FR/localise.php
oc-FR/language/oc-FR/localise.php
ps-AF/administrator/language/ps-AF/localise.php
ps-AF/language/ps-AF/localise.php
pt-BR/administrator/language/pt-BR/localise.php
pt-BR/language/pt-BR/localise.php
ro-RO/administrator/language/ro-RO/localise.php
ro-RO/language/ro-RO/localise.php
se-NO/administrator/language/se-NO/localise.php
se-NO/language/se-NO/localise.php
si-LK/administrator/language/si-LK/localise.php
si-LK/language/si-LK/localise.php
sq-AL/administrator/language/sq-AL/localise.php
sq-AL/language/sq-AL/localise.php
sr-RS/administrator/language/sr-RS/localise.php
sr-RS/language/sr-RS/localise.php
sr-YU/administrator/language/sr-YU/localise.php
sr-YU/language/sr-YU/localise.php
sv-SE/administrator/language/sv-SE/localise.php
sv-SE/language/sv-SE/localise.php
sw-KE/administrator/language/sw-KE/localise.php
sw-KE/language/sw-KE/localise.php
sy-IQ/administrator/language/sy-IQ/localise.php
sy-IQ/language/sy-IQ/localise.php
tk-TM/administrator/language/tk-TM/localise.php
tk-TM/language/tk-TM/localise.php
tl-PH/administrator/language/tl-PH/localise.php
tl-PH/language/tl-PH/localise.php
ug-CN/administrator/language/ug-CN/localise.php
ug-CN/language/ug-CN/localise.php
ur-IN/administrator/language/ur-IN/localise.php
ur-IN/language/ur-IN/localise.php
ur-PK/administrator/language/ur-PK/localise.php
ur-PK/language/ur-PK/localise.php
vi-VN/administrator/language/vi-VN/localise.php
vi-VN/language/vi-VN/localise.php
zh-CN/administrator/language/zh-CN/localise.php
zh-CN/language/zh-CN/localise.php
zh-TW/administrator/language/zh-TW/localise.php
zh-TW/language/zh-TW/localise.php

//edit list updated

Hello, everyone.

I'm developing a website, which is planned to be bilingual. But, I can't find the Indonesian language pack. What should I do? Do I have to make it myself? If yes, how can I make it?

Regards,

A.M. Marhaen

Belarusian core translate

action fails
see https://github.com/joomla/core-translations/runs/6122422975?check_suite_focus=true

CONFIGURATION GIT USER
fatal: unsafe repository ('/github/workspace' is owned by someone else)
To add an exception for this directory, call:

git config --global --add safe.directory /github/workspace

more information:

• https://github.blog/2022-04-12-git-security-vulnerability-announced/
• https://git-scm.com/docs/git-config/2.35.2#Documentation/git-config.txt-safedirectory
• actions/checkout#760

During check of php files in #371 GHA returned following php error

Parse error: syntax error, unexpected '*', expecting end of file in ./joomla_v4/translations/package/kk-KZ/administrator/language/kk-KZ/localise.php on line 6
Errors parsing ./joomla_v4/translations/package/kk-KZ/administrator/language/kk-KZ/localise.php

in general top of this file is broken.

Latvian, Slovak language packs show a yellow language version:

Like other language packs it should be 5.0.0.x, not 5.0.1.x to match the Joomla version.

Steps to reproduce the issue

1. Installation Estonian language pack 5.0.1.2
2. 'Updates are available' Home Dashboard
3. Update Estonian language pack 5.0.0.2 > 5.0.1.2
4. 'Extensions are up to date' shown – click on button show again 'Update Estonian language pack 5.0.0.2 > 5.0.1.2'

Expected result

Extension is up to date.

Actual result

After a few minutes 'Updates are available' shown again on Home Dashboard.

System information (as much as possible)

Linux lamp302.cloudaccess.net 3.10.0-962.3.2.lve1.5.81.el6h.x86_64 joomla/joomla-cms#1 SMP Wed May 31 12:07:35 UTC 2023 x86_64
mysql
8.0.34-cll-lve
utf8mb4_0900_ai_ci
utf8mb4_0900_ai_ci
None
Yes
8.1.24
Apache
cgi-fcgi
Joomla! 5.0.0 Stable [ Kuboresha ] 17-October-2023 16:00 GMT
Enabled (classes_aliases:"1", es5_assets:"1")
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0

As stated in this thread https://forum.joomla.org/viewtopic.php?f=708&t=994471 , it seems there's an issue in italian joomla language pack.

Best regards

Installation Kazakh language fails

JInstaller: :Install: Can't find Joomla XML setup file.
Unable to detect manifest file.

There are still 2 strings containing wrong placeholders of the type %S instead of %s (which breaks in 8.1)

from admin com_admin.ini

line 27 COM_ADMIN_EXTENSION_AVAILABLE="Disponibile %S"

from com_joomlaupdate.ini

line 173 INSTL_EXTENSION_AVAILABLE="Disponibile %S"

According to https://issues.joomla.org/tracker/joomla-cms/42342
the Danish (da-DK) language the file
administrator/language/da-DK/plg_sampledata_blog.ini is corrupt, b/c the lines with
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_0_TITLE aso. have to be unique for the sample blog data installation!
Suggestion (but I'm not a native speaker):

PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_0_TITLE="Millioner"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_1_TITLE="I hele verden"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_2_TITLE="Kærlighed"
PLG_SAMPLEDATA_BLOG_SAMPLEDATA_TAG_3_TITLE="Joomla 5"

I do not know if there is also another language file with equal tags in the repository?
Perhaps there an automated test to prevent this?
BTW the sample data are not translated from English to German (de-DE).

Hello, in the Indonesian language folder there are no files that can be downloaded. What do I have to do ?

Hello,

I need a langauge pack for Northern Mazedonia (mk) - it existed in Joomla 3, but does not in Joomla 4.

Can anyone help?

Thank you very much,
Michael

We get an error in install languages page because the language code is not available
Notice: Undefined offset: 1 in /Applications/MAMP/htdocs/stagingcms/administrator/components/com_installer/views/languages/tmpl/default.php on line 68

The reason is simple: the install xml are wrong on the server:
https://update.joomla.org/language/details3/kk-KZ)_details.xml => Extraneous )

(https://update.joomla.org/language/details3/kk-KZ_details.xml does exist.)

also 2 errors in translation list

<extension name="Kazakh" element="pkg_kk-KZ)" type="package" version="3.9.23.1" detailsurl="https://update.joomla.org/language/details3/kk-KZ)_details.xml"/>;

Hi
I suggest use GHA build matrix where possible - for example in crowdin v4 dl package translations. This reduces code duplication. For this workflow we can use matrix in crowdin action like this:

- name: Crowdin Download ${{ matrix.language-name }}
      uses: crowdin/[email protected]
      with:
        # Option to specify a path to the configuration file, without / at the beginning
        config: 'Configurations/Crowdin-J4-All.yml'
        # Upload sources to Crowdin
        upload_sources: false
        # Make pull request of Crowdin translations
        download_translations: true
        # Download specific language
        download_language: ${{ matrix.language-code }}
        # Only download translated strings
        skip_untranslated_strings: true
        # Include approved translations only in exported files. 
        # If not combined with --skip-untranslated-strings option, strings without approval are fulfilled with the source language'
        export_only_approved: true
        # The message of the commit
        commit_message: "New ${{ matrix.language-name }} Crowdin translations by Github Action"

and in matrix we define 2 arrays.

Steps to reproduce the issue

I have a clean installation of Joomla 4.0.2 with Italian language installed for frontend and backend.
The update system notifies me a language update available. I run this update, it is not carried out and after a few hours an update is available again the same update that I run, it tells me that it has completed the update but it is not so and still in loop.
I think Joomla fails to update the language.
I don't know if it has anything to do with this problem but the current language version is not detected.

Expected result

If I do an update it must actually be done.

Actual result

The update does not happen but it confirms that I have done it correctly.

System information (as much as possible)

Joomla 4.0.2
PHP: 7.4.23
MySql: 10.3.31-MariaDB-cll-lve

Marco Galassi

Before merging language updates we should validate the PHP files.
At least a syntax check should be done something like:

find . -name *.php -exec php -l "{}" ;

suggested in joomla/joomla-cms#35401

4.2.2.3 - 4.2.7.1
The date formats( DATE_FORMAT_* ) in the various joomla.ini language files appear to mixed [AU/GB] & US formats, causing an incorrect/invalid date on various article publishing dates (value/data attributes & display) in administration and subsequently causing issues with correct sorting in both Admin and Frontend.

Site:
missing ending doube quotes
COM_CONTACT_EDIT_PUBLISHED_CONTACT="已发布的联系人

Admin:

13 files do not escape double quotes correctly & other errors.

The previous conversion mechanism from &quote; too _ QQ _ must not be used with Joomla4.
Crowdin is rewriting the Joomla filetype processor on the Crowdin Enterprise platform, to remove this requirement.

I see there is no Urdu (pakistan) translation in Joomla, I want to contribute, tell me how I can do ?

Since tinymce has own translations for many languages they can be used to be automatically pulled in to joomla 5+.
Using the core translation as a single point for translation would make sense for me and also allows us to translate tinymce to languages which are not provided by upstream.

references:
joomla/joomla-cms#40418
joomla/joomla-cms#40408
https://www.tiny.cloud/get-tiny/language-packages/

Ndonga, also called Oshindonga, is a Bantu dialect spoken in Namibia. It is a standardized dialect of the Ovambo language. has a large number of speakers in Namibia and widely taught in Schools as a first language.

Other willing contributor: @Amunwe-ENE

Joomla! doesn't have support for this language, Please create setup for Ndonga so that we can contribute translating Joomla! CMS. @Amunwe-ENE and I are native Ndonga speakers with proficient understanding over it.

List of its language codes:

Dari language code should not be fa-AF as this code is a IETF code. Until now, we use ISO codes for Joomla languages.
The real ISO Code is prs-AF as in J3.
See https://en.wikipedia.org/wiki/Dari

This should be modified in all xmls and the crowdin list of languages and also explained to the TT coordinator for this language.

Once again multiple errors in this language pack are causing errors. Today alone there were two bug reports to core which were just errors in this language pack.

I randomly checked three files and ignoring issues with strings not being 100% up to date I found strings in Russian, Polish and others that were simply wrong and copy pasted from the wrong place.

#35 was the previous report.

These are are just copies of en-AU.

BUILD_INCOMPLETE_LANGUAGE="English AU"
BUILD_NOXML_LANGUAGE="English AU"
BUILD_MIN_PHP_ERROR_LANGUAGE="English AU"

Example for en-NZ, the value English AU should be English NZ, etc.

Message send to Crowdin:

One of your colleagues came with the nice suggestion / solution, to add ; comment behind a string.
Like this:

PLG_FIELDS_IMAGELIST_PARAMS_DIRECTORY_DESC="This directory is relative to \"images\" directory in Joomla! root." ; Don't translate \"images\"OR:
PLG_FIELDS_IMAGELIST_PARAMS_DIRECTORY_DESC="This directory is relative to \"images\" directory in Joomla! root." ; Don't translate "images"

Only the parser breaks at the moment and only works if we remove the " or any other "
The comment is added to the string to be translated.The only thing working is:

PLG_FIELDS_IMAGELIST_PARAMS_DIRECTORY_DESC="This directory is relative to \"images\" directory in Joomla! root." ; Don't translate images

We already changed a lot of our source files in the product.
Which we can't just correct.
Can you fix the parser?