Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Join efforts with wv_deepltranslate to maintain only one extension in the future? #13

Open
sypets opened this issue Aug 25, 2021 · 0 comments

Comments

@sypets
Copy link

sypets commented Aug 25, 2021

Thanks for providing the extension! I think it is awesome and a very cool feature if you work with translations.

I do however have a request (a wish):

When I first looked at an extension for DeepL (I think it was for TYPO3 v9), I tested deepltranslate, it didn't work, then I tried the wv_deepltranslate extension, it worked and I stuck with it. Apart from a few feature requests (see issues and PR) it is what I was looking for and works reliably.

However, for everyone else or especially new people it is not a good situation: You have 2 extensions in TER, you don't know what to use, what will be maintained long term etc.

Is it possible to discontinue this extension and make wv_deepltranslate the default and join forces? (or vice versa)?

It might be possible to do something like this (to abandon one package and switch to the other):

image

You will also see a message working with Composer that one package is abandoned and the other should be used.


I think everyone in the community would benefit from something like this in general.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant