standardize gettext, .po, po terminology (follow-up issue to locale collect project information)

Created on 4 September 2012, almost 13 years ago
Updated 19 July 2023, almost 2 years ago

Based on webchick's initial comment
#1627006-56: Collect project information for translation update β†’
+++ b/core/modules/locale/tests/modules/locale_test/locale_test.moduleundefined
@@ -0,0 +1,27 @@
+ * Simulate a custom module with a local po file.
Just in general, we call these gettext files, .po files, and po files. It'd be nice to standardize on one terminology.

πŸ“Œ Task
Status

Active

Version

9.5

Component
LocaleΒ  β†’

Last updated 4 days ago

Created by

πŸ‡ΊπŸ‡ΈUnited States yesct

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Wonder if this is still a needed task for D10?

  • Status changed to Active almost 2 years ago
  • πŸ‡ͺπŸ‡ΈSpain penyaskito Seville πŸ’ƒ, Spain πŸ‡ͺπŸ‡Έ, UTC+2 πŸ‡ͺπŸ‡Ί

    Naming things consistently in core code and comments will always be wonderful. Definitely not a top priority at the moment, but anyone can work on this if desired.

Production build 0.71.5 2024