[wp-trac] [WordPress Trac] #41256: Core hardcoded translations

[WordPress Trac]

#41256: Core hardcoded translations
-------------------------------------+-----------------------
 Reporter:  sisalik                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  I18N                     |     Version:
 Severity:  normal                   |  Resolution:  invalid
 Keywords:  reporter-feedback close  |     Focuses:  template
-------------------------------------+-----------------------

Comment (by niclovincent):

 Given the prevalence of hardcoded text strings like 'Search', 'Search
 results for', 'Tag', 'Tags', 'Category', 'Categories', 'Pages', etc., in
 WordPress templates (Pages, Posts, General), there is a need to implement
 a more flexible localization strategy within the WordPress core.

 Would it be beneficial to introduce a function within WordPress core that
 dynamically checks for language tags (e.g., hreflang or URL indicators) to
 fetch translations from a centralized language table/file? This approach
 would enable seamless integration with translation plugins and facilitate
 the addition of custom languages. Additionally, providing an admin
 interface to manage languages within this system could greatly enhance
 user experience and mitigate issues with hardcoded translations being
 overwritten during WordPress updates.

 This enhancement would not be a translation plugin but an integral part of
 WordPress core, ensuring a more robust and adaptable localization
 framework. What are the core team's thoughts on integrating such a dynamic
 localization mechanism into future WordPress releases?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41256#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform