英文:
What are the correct (convention) TYPO3 language fields?
问题
有人能澄清 TYPO3 中语言字段的正确和传统字段是什么吗？
我看到了各种各样的字段，例如：
l10n_parent
i10n_parent
l18n_parent
i18n_parent
... 其他 l10n_ 字段也是如此
现在文档（TYPO3 12.4）说：“...可以更改这些字段的名称（...），但这是强烈不建议的，因为它违反了约定（...）”。
然后文档解释了字段 sys_language_uid、l10n_parent、l10n_source、l10n_diffsource。有一些说明说：“*有时出于历史原因使用 l18n_diffsource”。
然后有这个 示例，让我完全困惑了。有一个列为 l18n_parent 和（历史上的？）l18n_diffsource。难道不应该都以 l10n_ 开头吗？
另一件事是 l18n 本身（小写的“L”）。如果这应该是“国际化”的数字缩写，那么字段名称不应该以 i18n_... 命名吗？
我认为文档中这部分的作者混淆了 l18n（小写L）和 I18n（大写I），在大多数字体中它们看起来一样，并且 l10n 实际上以小写的“L”拼写是正确的。
谢谢 
英文:
can someone clarify what the correct, conventional fields are, for language-fields in TYPO3?
I See all kinds of this for example:
l10n_parent
i10n_parent
l18n_parent
i18n_parent
... same for the other l10n_ fields
Now the documentation (TYPO3 12.4) says "...It is possible to change the names (...), however this is strongly discouraged as it breaks convention(...)"
Then the docs explains the fields sys_language_uid, l10n_parent, l10n_source, l10n_diffsource.
Some note says "Sometimes l18n_diffsource is used for (...) historic reasons"
Then there is this example, that completely confuses me. There is a column for l18n_parent and the (historic?) l18n_diffsource.
Shouldn't both start with l10n_?
Another thing is te l18n itself (with an lowercase "L"). If this should be the numeronym for "Internationalisation", shouldn't the fields are named with i18n_...?
I think the writer of this part of the docs confused the l18n (lower L) and I18n (capital i), which looks the same in most fonts, and the case that l10n is actually correct with a lower "L".
Thank you
答案1
得分: 3
您说得对，l18n_parent 是 tt_content 表中的错误。这很可能是由于本地化（l10n）和国际化（i18n）的混淆而引起的。出于历史原因，这个问题仍然存在，而且要修复为在所有其他表中使用的 i18n_parent 需要付出巨大的工作量。这就是为什么它今天仍然以这种方式存在的原因。
英文:
You are right that l18n_parent is an error in the tt_content table. It is likely caused by a confusion of l10n and i18n. This still exists for historic reasons and the expected amount of work would be huge to fix this to i18n_parent as used in all other tables. That is why it still exists like this today.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论