SkyLundy
commented
2 years ago There was some discussion in the forums about this but the idea wasn't pursued for a couple of reasons. Primarily because ProcessWire is built around a primary language with secondary languages and the module follows that design. I also wanted to focus on core functionality before expanding the features.
One of the reason's that the general translator tool up in the menu bar was placed there was to allow for more free translations between languages and help translations in the situations like you mentioned. It was a faster solution that might have more flexible use.
Initially I had planned for cross translation on a per-field basis but wanted to focus on finishing the module. This feature could be re-approached after the module gets out of alpha and has more use/testing on more websites. In the meantime making use of the translator tool in the menu bar would be the best idea. I designed it so that it opens in a popup and doesn't lose your place where you are editing content.
This idea could come back up in the future.
ivangretsky
Good day @SkyLundy ! Thanks for an essential module for a multi language site! I have installed it yesterday and already love it.
I want to suggest an enhancement - the ability to to translate from non-default language. On our site the default language is English. Still a lot of content is primarily filled in different language. So we need to translate content from non-default to default.
I think it should be possible. The UI for this could be implemented as a dropdown under the field instead of a single link.
What do you think?