New name for this plugin; brainstorming and choosing

[MPolleke]

Hi, very interested in this effor to revive qTranslate. :) I saw the discussion on: https://github.com/qTranslate-Team/qtranslate-x/issues/579 I think it would be good to gather ideas (brainstorm phase) and hopefully pick a good name. That way there can be an effort to rename the project, and maybe rename functions and settings (if desired). Just trying to think along.

Some ideas gathered from the old linked issue:

• openQtranslate (mayaliny)
• qTranslateXXL (probably trademark issue) (mayaliny)
• qTranslate-CE (Community Edition) (probably trademark issue) (abclution)
• qTransferendum (Translate in Latin) (Ruaphoc)
• qTranslate-NG (as in Next Generation) (probably trademark issue) (Ruaphoc)
• qTranslate-WP (probably trademark issue) (Ruaphoc)
• KUKU translate (Italian "q" sound like "ku") (mayaliny)
• qTraduki (qTranslate is esperanto) (mpolleke)
• Inline Translator (wisamx)
• itranslator (wisamx)
• itranslate (wisamx)
• Decipher (too deep?) (emyawasap)
• NewTranslate (phil4literacy)

More ideas are welcome. My preference so far would be qTransferendum, since latin is not a living language anymore and avoids confusion among live speakers.

If it turns out the old slug at wp.org can be used, all the better. If that is not possible or unwanted, a new name is needed.

[herrvigg]

You're much welcome to join this resurrection project! As i see it, qTranslate-XT is only a "bridge" project the time to clarify how it will evolve in the future. Actually i like this name because it reflects well the current state. As i see it for the future, there are two alternatives:

• we somehow manage to get the right to update the old qTranslate-X slug. In that case the official name of this plugin should also turn back to qTranslate-X. As everybody knows the author disappeared so it's problematic. There might be some possibility to discuss with Wordpress about the trademark but first we need to focus on new releases, both fixes and new features.

• if we can't re-use the old slug then yes we'll need to move out to a whole new one. To be accepted by Wordpress it has to be quite different, i think they are becoming a bit stricter (and that's a good thing imo). At this point we may even abandon completely the qTranslate legacy.

For now i think we can continue working on this new repo safely without having to care too much about the name. The license is open source so this work should not be lost in any case. I would like to see this project managed by a real team and an indepedent community without any commercial aspect. If some want to develop extra stuff on top of it then it's fine but it shouldn't impact the core plugin.

[rinurinu]

Cool suggestions so far! If I understand it correctly it cant start with qTranslateX because of the wordpress plugin guidelines, right?

[MPolleke]

That i correct. It is considered a trademark and cannot be used as name or at the start of the name.

[herrvigg]

Well i have to rediscuss with the plugin managers at Wordpress. Creating a new plugin with a different name is the second option, we would also need to repackage a lot of stuff and make it clearly different.

But, in some cases, such as when the author disappears, it seems we can be given the right to update the official plugin. However this doesn't give the right to claim the trademark so it can be a bit touchy.

For now it's not very important, we should focus on the code with new fixes and features. In any case we need considerable changes before we can take any of the two options. So we should start thinking about a roadmap. On the readme i mention what i think are the most important features to come: Gutenberg, translatable slugs, WooCommerce.

[wisamx]

What characterize qtranslate is that it uses in-same page translation. So i feel the name should have something related. Like: inline translator, itranslator, itranslate.

[mikhailnathanielabordo]

I was thinking of decipher but I think it was too deep.

[dschmidtke]

HI, I suggest newTranslate, since it sounds very much like qTranslate and it's indeed new. Easy. I use qTranslate-x in some own and client's projects, so I want it to survive, and I am willing to contribute code to this fork.

[artisanphil]

I like the name newTranslate.

[Peter-HVD]

Like I said on https://github.com/qTranslate-Team/qtranslate-x/issues/579 it's fairly straightforward to take over an obviously abandoned plugin. Personally, I'd concentrate on getting that sorted for now and worry about the name later. It might well be that the "trademark" never gets questioned. If it ever does, deal with it then.

[herrvigg]

Yes the name is a secondary question for now and even the WP repo. First i would like to get some feedbacks on the new release. Have you people tried QT-XT?

[Peter-HVD]

Hi Herrvigg. I've installed it on a test site, replacing the original. It's not a production site, so little more than a few test posts and no coded enhancements, but it worked perfectly. No errors so far! I have a major project coming up in a month or so to do some serious code updating to an existing site that used qT-X. That'll be the big test :-)

[wimstefan]

Same here. Switched on my development environment to QT-XT and all works so far. But I have to admit that I didn't really test it to the max ...

[MPolleke]

I tried it and it seems fine. I also tried adding support for the WP 4.8+ Text widgets, but everything is quite connected with everything, and it seems to be a bit over my head to contribute code.

[herrvigg]

For the future my intention is to move to a new repo abandoning some of the new qTranslate-X legacy. I've been struggling quite a bit to clean up this project but it's a quite a big mess when it comes to the integration! The new project must be easier to maintain so i feel i have to refactor quite many things and probably discard some legacy stuff. For the moment i'm still on qTranslate-XT as a transition phase and doing some experiments with Gutenberg but from a certain point i feel this project needs a real new start to be able to live on the long run. So yes the question of the name will come back again soon :P

[herrvigg]

Just a short update, i'd say there 3 topics to address before moving this repo to an official plugin:

• differentiation: it should be different enough from the original plugin. Though the old one is dead and i provided some fixes it's not enough yet. The main news coming in are the new modules for better integration but the most relevant would be the support of Gutenberg. It's not been my priority for now but for more news see https://github.com/qtranslate/qtranslate-xt/issues/605.
• qTranslate "branding". I don't own it and as the previous author simply disappeared (who knows what happened?) i think it's better to find a new name as proposed here. The drawback is that the previous users might be a bit confused, it's still the main qTranslate line. I have not a clear answer on this yet.
• refactoring and tests! This is a crucial point. Creating a new plugin should be the opportunity for a DEEP refactoring. From my point of view, the current code is a terrible mess, it's barely maintainable and even a small change becomes a big headache. We should refactor the internal files to classes, add dynamic loaders, redesign the whole interface for better integration both in PHP and JS. We need unit tests, possibly integration tests (see https://github.com/qtranslate/qtranslate-xt/issues/620). It must be better documented. There's a lot to do but the crucial part is definitely the integration / API. A new plugin should redefine a clean interface even it means to break some compatibility (this repo can still be left for retro-compatibility). From this point a new plugin would really make sense.

Until then this repo is good enough imo. I know some end-users might not like the fact to use github and maybe would feel better (?) with an official plugin but it shouldn't be such a big deal. It's more important to make this one evolve and recently there is more activity from many github users so that's a good news! I never pretended to this alone ;)

[majekw]

@herrvigg , lets face the fact that you are maintaining qTranslate-xt for over 8 months. Just stick to current name as many people already know continuation of qTranslate under this name. Give up attempts for taking over qTranslate, mqTranslate or qTranslate-X Wordpress repositories, it's waste of time in my opinion. As for refactoring and tests - Rome wasn't built in a day, just keep doing your great job, but don't wait for this piece of software to be perfect before official release. Once again, thank you for your great job and I'm looking forward to see qTranslate-XT directly in Wordpress plugins.

[herrvigg]

Ahah i was currently writing this long message at the same time! I'm actually thinking to abandon the name qTranslate-XT.

Indeed the status of this project as qTranslate-XT is starting to get problematic (e.g. the last PR for composer). Also it would help to become a new official plugin available at wordpress.org. The current version seems to be working good and i understand it's a relief for many. I'm fine to continue helping with the transition, it should and can be done gradually. And there's a lot to do.

The problem is that i can hardly push it as qTranslate-XT, the new rules with WordPress are a bit harder, and that's a good thing. We can't have qTranslate as prefix because it's considered by WP as a trademark. In the best case it would be with a new prefix to get around it but that's just a kind of trick.

Strictly speaking, to take over qTranslate we'd need to get the approval of the owners to keep the brand. Problem, as everyone knows, they are not active anymore. As i see it they are two: John Clause for qTranslate-X and Qian Qin for qTranslate who actually wrote most of the code still in use. I suppose qTranslate comes from his name, correct me if i'm wrong! But John Clause doesn't respond and Qian Qin also abandoned the project long ago.

For that reasons and to avoid any speculation it's better we finally abandon qTranslate in the name and rebrand it. The previous authors made a huge contribution to this project but we need to move forward. They will be credited as deserved. The drawback is that we might lose some users by fear of a big change but it's better to move on. If the tool is good, people should find it again.

So let's restart some brainstorming!

[herrvigg]

Here a few points of discussion:

• The names newTranslate or openTranslate sound a bit too generic to me. Clearly the code will remain open source as most of the WP plugins so we don't need to repeat that.
• I like the idea that the name should represent what makes this tool unique. As mentioned by @wisamx the core idea is in-same page translation. So the name could have something to do with concept as: fusion, assemblage, aggregate, blend, joint, ... Maybe even something with buffer.
• Translate is a bit long to spell. I love the term "lang" which might be easier to combine. But you can try to substitute if it sounds better.
• We might have a dash, special character or upper case for a better look. But these are just minor variations for "styling".

So here are a few ideas coming on the fly: fusedlang, langfused, langfusion, agglang, aggrelang, assemblang, langblend, blendlang, unilang, langutd, langembed, langbuff, bufflang, langbuffet.

Also, another way to keep a "soft legacy" to qTranslate would be something like: something--qtlang, lanqtxt, langcutie, cutielang, langcutee, cuteelang. But this is more for fun ;)

Other suggestions? Someone has a better inspiration?

[majekw]

Ok, I see your point. For me qtlang or even qtlang-xt (to have better recognition for current users od qTranslate-XT) is fine. cuteelang is cute :-) So, that's my votes.

[alphp]

langPanels, multiLangPanel, langSideToSide I'm not very witty today ...

[artisanphil]

I also like qtlang, although I find "openTranslate" is a good name too, as there are also commercial plugins.

Philip

On 05.03.19 07:33, majekw wrote:

Ok, I see your point. For me |qtlang| or even |qtlang-xt| (to have better recognition for current users od qTranslate-XT) is fine. |cuteelang| is cute :-) So, that's my votes.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/qtranslate/qtranslate-xt/issues/601#issuecomment-469470702, or mute the thread https://github.com/notifications/unsubscribe-auth/ANcHlZCjMplygafzj2OE5YUYAKkl92ctks5vTa08gaJpZM4VyVYG.

[Ruaphoc]

the assumptions so far are that everyone uses English. Let's not focus on English words/names. Latin is the foundation of a large number of languages, so why not a Latin name? We could shorten the Latin words to make them more appealing:

Change Language -> mutatione linguarum

so why not:

MutaLingua

Greg

[wimstefan]

That's a nice idea! Staying in that line of thought another word popped up immediately in my mind: "TransLingua"

[herrvigg]

I'll give a bit of time before deciding for a new name.

Meanwhile i have other questions coming up with the brand migration.

[herrvigg]

Edit: i moved those questions to a new ticket https://github.com/qtranslate/qtranslate-xt/issues/648. Let's only discuss about the name here.

[Ruaphoc]

I actually really like the “TransLingua” suggestion!

[bagaweb]

TransLingua sounds quite weird in Italian... Something like Transgender's tongue...

[alphp]

I am Spanish, and although it is true that someone who was badly thought could distort TransLingua, I think it will be anecdotal.

[Peter-HVD]

I recently came across this word - Metaphrase, which means a "literal translation". I think that sounds pretty apropos. If you wanted to tie it back to the original, maybe qMetaphrase?

[herrvigg]

I also speak italian and i agree TransLingua sounds weird. I must say i'm not fan of the Lingua term because it refers more to the tongue as organ than language in many... languages 😛

[alphp]

In Spanish there is a word ending in lingus that is not suitable for all audiences.

In that sense, I prefer English, it's more neutral.

I like CuteTranslate ( @TheHeat in https://github.com/qtranslate/qtranslate-xt/issues/648#issuecomment-470200007 ) because it sounds good and is reasonably similar/different to qTraslate.

[Blackbam]

How about DirectTranslate or InstaTranslate (or something similar)? I think it would describe the Plugin best, as there is no unnecessary duplication of any content. Just the text within a post or fields which belong to a post are translated.

[herrvigg]

So far i like Cute Translate most :) CUTL!

[herrvigg]

What sounds/look best, Cute Translate or CuTranslate?

[Blackbam]

Not sure XD

[reddo]

What sounds/look best, Cute Translate or CuTranslate?

CuteTranslate

[TheHeat]

I think the simpler Cute Translate will be easier for people to remember - the success of a plugin often relies on users being able to recommend it to others and often a name that is concatenated or 'too clever' risks completely passing people by. I say this as someone who's previously run a business where every time I told someone the name I had to spell it. It's a drag.

Better to keep it simple

[pszurgot]

CuteTranslate is cool :)

[dschmidtke]

CuteTranslate is fine, since it sounds very much like the original name qTranslate.

[wimstefan]

If I have to choose between the two CuteTranslate it is! 😏

[almendro]

my vote for CuteTranslate

[damen02]

Hi everybody. What a good news that this project is alive again!

I agree this may be not a priority by now, but it's still important. I have some experience on naming things like projects, products, and other stuff (have a background on branding, graphic and web design).

Here are some ideas that could help.

• One point to consider is de ease of pronunciation. When you read a word your mind "says it" as part of the process of memory retention. For example, cuteTranslate looks good in concept, but is tricky for speaking.
• The reference to parent project is nice tribute, but don't try to reference too many things because it only works on creators minds.
• Simplicity is always good, think about future name addons. But don't forget to be unique. That said, something like "qLang" sounds a good option to me. It is simple (like the spirit of this project), brief still unique, reference to original, simply to say, easy to remember, and easy to get a nice logo.

Thanks a lot to contributors and goog luck!

[herrvigg]

That's a good point, maybe cuteTranslate is a bit too long. I like the idea of something short so you can also think of extensions derived from it.

[bmachuel]

What about ez-lang?

--
Benoît Machuel

De: Herr Vigg notifications@github.com(mailto:notifications@github.com) Répondre: qtranslate/qtranslate-xt reply@reply.github.com(mailto:reply@reply.github.com) Date: 26 avril 2020 at 15:33:27 À: qtranslate/qtranslate-xt qtranslate-xt@noreply.github.com(mailto:qtranslate-xt@noreply.github.com) CC: Subscribed subscribed@noreply.github.com(mailto:subscribed@noreply.github.com) Sujet: Re: [qtranslate/qtranslate-xt] New name for this plugin; brainstorming and choosing (#601)

That's a good point, maybe cuteTranslate is a bit too long. I like the idea of something short so you can also think of extensions derived from it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub(https://github.com/qtranslate/qtranslate-xt/issues/601#issuecomment-619550445), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ABTBFXCJU3GTBZTBOTF4XV3ROQZ2PANCNFSM4FOJKYDA).

[alelkin]

QML - QMultiLang

[herrvigg]

Before we can make any migration to a new repo and make the plugin official we should decide for a good name so let's try to make some progress here.

@damen02 raised some good points. Indeed maybe we don't need to keep the reference to qTranslate in the name, most of the current users will find the new plugin from here even if it has a different name. If there are enough users downloading it, it doesn't really matter. The legacy for the previous contributions will remain clear but we move now to something new and we should look forward!

I also like the idea that the name should be easy to pronounce but we also want the name to tell something about the nature and/or the spirit of the project.

I'm more in favor of using a lang particle rather than translate because it's shorter. Also, translation is not really what this plugin is about, since you have to do the translation by yourself. What the plugin really does is to handle the different languages in single post or fields. It's about managing the content for edition, storage and display. I want the plugin to remain free, open source and community-driven.

We should differentiate the name from the main other "concurrent" ones: WPML (WordPress MultiLingual), Polylang, Weglot. The other plugins are rather about translation.

Here are a few new suggestions coming to my mind:

• OpenLang or OpLang to focus on the open-source aspect, the second version being more compact
• Populang or PopuLang which can be seen as a contraction of popular or population with language
• EasyLang or EaseLang in the same fashion as ez-lang or EzLang proposed earlier

I tried some combinations to refer to the technical functionality (single post) with words like: embedded, tag, block, composition, compound but it doesn't really work. Block is rather a reserved word now referring to the block editor Gutenberg and we are not handling this on the block level yet.

[Ruaphoc]

EasyLang gets my vote, or we could use SimpleLang.

[wimstefan]

Tinkering over your wish to have lang as main part of the new naming and being easy pronounceable I came up with "LangWhich" as a name ... it's pronounced the same as language but also includes the possibility which language to choose.

I hope this is not too silly but I thought I'd mention it anyway ...

[Blackbam]

One of the greatest benefits of qTranslateXT is that you do not have to duplicate posts and you also do not have to duplicate the whole page (which is especially awesome with custom eCommerce websites and post types in general that have a lot of meta data which does NOT have to be translated).

Therefore I like EzLang or EzTrans because the simple task of translating a website which is 95% the same content should not overcomplicate things.

[bagaweb]

I'm more in favor of using a lang particle rather than translate because it's shorter. Also, translation is not really what this plugin is about, since you have to do the translation by yourself.

Totally agree with you.

I'd vote for EasyLang or OpenLang.