Once #49 gets in, what stopping us from using entity translation instead of content translation
Pros: unified way of handling translation (nodes, taxonomy, ...) no need of i18n
Cons: still hard to manage translations of menu, block and other things
Related - https://github.com/backdrop/backdrop-issues/issues/4198 Content translation improvements
As people weigh in here with reasons they prefer (or were forced) to use entity translation, I would love if it we could add those reasons to that issue too -- since many of those improvements will be able to be included before 2025 :)
GitHub Issue #:
52
Recent comments
When logged in: On a page with a path prefix it shows the language of the prefix. On the front page if I add the path prefix it shows the language of that prefix...
Language negotiation only working when logged in
Hi! The description is still very vague and lacks step-by-step instructions on how to reproduce. It doesn't include the version of Backdrop either, nor a list of contrib modules you are using...
Problems with HTML content and text formats
Sorry, it did seem confusing when I read it back... So if I add some html to a text field, for example in a page or a block, whatever the text format of the field may be (raw html or basic...
Problems with HTML content and text formats