>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3339013. --> Reported by: [joseph.olstad](https://www.drupal.org/user/1321830) Related to !23 !22 !10 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <h4>Summary</h4> <p>This functionality used to exist in jquery_ui 1.x via jquery_ui_datepicker 1.x.</p> <p>This issue was raised in order to bring back this functionality into jquery_ui 2.x.</p> <p>The jquery_ui_datepicker module used to have translations via the drupal ui, please see merge request 10 that restores this functionality.<br> <del>First pass at making i18n work concludes it only works in one language , my first attempt at patching jquery_ui resulted in a one language for all, choose that language and unable to switch between translations.</del></p> <h3>Current status</h3> <ol> <li>Merge request 10 restores the expected functionality. <del>No localisation for datepicker</del></li> <li>Merge request 10 restores the expected functionality. <del>No Drupal.t support (<strong>our preferred approach</strong>)</del></li> <li>Merge request 10 restores the expected functionality. <del>No jquery_ui i18n/ i18n folder is missing <strong>(better than nothing approach uses browser preference not Drupal)</strong></del></li> </ol> <p>Thank you to bnjmnm for restoring this functionality. <del>prefer the approach used in the jquery_ui_datepicker 1.x release.</del></p> <p>@G&aacute;bor Hojtsy , </p> <p><del>In the jquery_ui_datepicker 1.x branch the months, weeks and days were translated using Drupals t() function. This allows the date calendar weeks/days/months labels to match the language of the Drupal interface language rather than using the jquery_ui approach of loading the calendar language based on the browsers declared locale which stays the same on any Drupal translation. So if your locale is english you'll see an English calendar on a french or german translation. We prefer the calendar matches the Drupal interface language. However jquery_ui currently doesn't even have ANY locales, there's no i18n folder , no locales at all so we get zero locales except English.</del></p> <p><del>The jquery_ui_datepicker 1.x approach is desireable to us because it uses Drupals t() function for weeks, months, labels and respects the interface language for the current page and we like this approach. However the jquery_ui_datepicker 2.x branch is an empty shell, and relies 100% on the jquery_ui module to do the datepicker and the jquery_ui module does neither offer the i18n versions of the jquery datepicker nor does it use the t string approach that the 1.x jquery_ui_datepicker module used. </del></p> <p><del>So basically if you use jquery_ui simultaneously with the 2.x branch of the jquery_ui_datepicker module then you have no localisation for the datepicker. The 2.x branch of the jquery_ui_datepicker is basically offloading everything to jquery_ui and whoever published the jquery_ui_datepicker 2.x branch gutted everything from 1.x in favour of some new approach which lacks localisation.</del></p> <p>This is the shortenned summary of the situation.</p> <h3>Here is what we expect:</h3> <p><img src="https://www.drupal.org/files/issues/2023-02-06/a_datepicker_localized.png" alt="what datepicker should look like"></p> <h3>Here is what jquery_ui module gives us instead:</h3> <p><img src="https://www.drupal.org/files/issues/2023-02-06/jquery_ui_gives_us_this_instead.png" alt="jquery_ui gives us this"></p> <p>So in addition to having no translation at all is that the default jquery_ui solution (even if it was implemented) normally relies on the browser language rather than the Drupal interface language. jquery_ui_datepicker 1.x solves all of this. See the source code for jquery_ui_datepicker how it uses Drupals t functions for the labels.</p> <p>So I've downgraded to jquery_ui_datepicker 1.x latest and jquery_ui_effects 1.x latest and am using patches to upgrade the library to 1.13.2<br> This resolves the issue for D9, but it will likely become a problem in D10 if we're forced to use the new approach.</p> <h4>Motivation</h4> <p>We need the date picker to work in our language but jquery_ui module does not include the assets/vendor/jquery.ui/ui/i18n folder<br> tested this approach, the hook being used runs only once per cache rebuild. I'm not sure where to intercept the library on page load and load the expected i18n js file. I was only able to hack in my chosen language over top of all others.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h4>Proposed</h4> <p>a dirty solution is to add the jquery ui i18n folder but would prefer drupal t strings, with that said, i18n folder <del>is going to work we can deal with improvements later this should be adequate.</del><br> <strong>Tested this approach and it doesn't work as expected, can only override english with one other language and then english is lost</strong></p> <h4>reproduce:</h4> <p>install jquery_ui, visit the date picker using a drupal interface language OTHER than english<br> the months and days show up in ENGLISH only. So far patching has only permitted substituting english with one language and then stuck with that one language choice.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><del>Include the i18n folder with all the languages</del></p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>write a patch and review</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>expected labels for months and days should show up</p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>N/A</p>