Project

General

Profile

Actions

Task #100031

closed

Inconsistency of naming transOrigDiffSourceField fields (l18n_diffsource should be i18n and l10n_diffsource)

Added by Sybille Peters about 1 year ago. Updated 7 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2023-02-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
microcopy, naming conventions, internationalization, localization, l10n, i18n
Complexity:
Sprint Focus:

Description

  • AFAIK l18n (with an L as in Localization) is not the convention , it is i18n (with an I as in Internationalization)
  • why use both?
  • shouldn't i18n_diffsource (i18n for Internationalization) be more appropriate (see source below)?

The following field names are currently used for transOrigDiffSourceField:

sys_file_metadata.php:   => 'l10n_diffsource',
sys_category.php:        => 'l10n_diffsource',
sys_file_reference.php:  => 'l10n_diffsource',
pages.php:               => 'l10n_diffsource',
sys_file_collection.php: => 'l10n_diffsource',
tt_content.php:          => 'l18n_diffsource',

Localization refers to the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market (a locale). Localization is sometimes written in English as l10n , where 10 is the number of letters in the English word between l and n.

Internationalization is the design and development of a product, application or document content that enables easy localization for target audiences that vary in culture, region, or language. Internationalization is often written in English as i18n , where 18 is the number of letters between i and n in the English word.

https://www.w3.org/International/questions/qa-i18n


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Epic #101557: Translation Handling FindingsNew2023-08-03

Actions
Actions

Also available in: Atom PDF