[Feat] Provide method to sync from other projects

[ConfusedVorlon]

Problem Statement

I typically have a bunch of plumbing which is common between my various apps.
It would be nice to be able to tell Remafox 'go hunting in my other Remafox Projects for pre-existing translations.

Suggested Solution

Perhaps a checkbox/option in the button to fill in empty translations
'look in other projects first'

[Jeehut]

@ConfusedVorlon This is an interesting feature idea, but I'm not sure how you mean it exactly. I could imagine:

A: While creating the key in the Add Translation window, you want some button that opens a Strings search interface for your own Strings so you can import them.

B: Much like the #55 feature for common translations, you want to be able to build "your own common translations". So, this would be more of an addition to the common translations feature, making it more flexible. The idea is that you would be able to reference these directly within your apps without having to add a new key. (Technically, RemafoX adds the key for you if you reference it in your project.)

Which one do you mean?

[ConfusedVorlon]

For me, it's more about B.

I want to click a button that says something like

translate everything, and use the following priorities for sources:

1. My own translations from existing apps
2. Other common/standard translations
3. Machine translations

When combined with my other suggestion about annotating translation sources, then there is potentially an ability for RemaFox to 'upgrade' translations as new info comes along.

e.g. RemaFox would say
String A was machine translated
but I have a manual translation from Project B, so I'll upgrade to that.

Managing the complexity of this from a UI point of view might be tricky - it could easily spiral out of control!

[ConfusedVorlon]

essentially, the 'insight' that I'm wanting to apply is that for a given string; a manual translation in one of my other apps is probably more likely to be correct than a machine translation.

[Jeehut]

@ConfusedVorlon I see, thank you for the additional explanation. I think I understand your use case better now. I will consider it when working on a feature solving your use case. Thanks for you time! 👍