Updated: Comment #1
Problem/Motivation
Multilingual support for node base fields at storage level was added in #1498674: Refactor node properties to multilingual , but there is still no way to enter multilingual values from the UI.
Proposed resolution
After the changes introduced in #2004626: Make non-configurable field translation settings available in the content language settings , we just need to mark node base fields as translatable in ther definitions and verify that everything works as expected.
Remaining tasks
- Write a patch
- Verify that multilingual nodes behave correctly
- Fix any outstanding issue
- Add test coverage
- Reviews
User interface changes
All translatable node base fields appear in the content language settings page.
API changes
None
Related Issues
#1498674: Refactor node properties to multilingual
#2004626: Make non-configurable field translation settings available in the content language settings
#2019055: Switch from field-level language fallback to entity-level language fallback