Open LC43 opened 9 years ago
@xhaleera any thoughts?
I'm in the process on integrating all improvements of qTranslate-X into mqTranslate, in order to enhance interoperabiltiy and potentially merge the two plugins in the future.
Hi, Some days ago I've read this post from @xhaleera in mqTranslate support forum: https://wordpress.org/support/topic/2015-what-to-expect-for-mqtranslate
I think merging mqTranslate with qTranslate-X is a very good idea, why not all these alive platforms join forces and keep a main opensource multilanguage platform alive. I've been watching the gradual syncing between these two forks, and I'm very happy with it for several reasons. As a translator I've been helping to maintain my native language files translated in mqTranslate, the moment I've known these two where willing to merge, I started to import my translation files into qTranslate-X and found they where already very similar, as most of strings got already translated. Meanwhile, as a user of Qtranslate Slug also, I've been doing the same translation work, as some translation strings related debugging.
In my opinion, as I see qtranslate-slug being very well maintained with compatibility with both mqTranslate and qTranslate-X, as these to forks merge, the double effort will be reduced. I think this great effort to make one great platform with more active developpers is a very good opportunity to think about merging Qtranslate Slug also, as it could very well stay as an option, and the effort of developing it outside as a subplugin might be superior than integrated in one single system. Another reason I think this might work is because @LC43 @xhaleera and @johnclause are already working together making these plugins compatible with each other.
A few days ago I found another platform: https://wordpress.org/plugins/multilanguage/ But for me, I like it much more the way you guys have been developing your plugins, mqTranslate kept alive after original qTranslate got old, Qtranslate Slug for the very nice job in adding a great feature and making it compatible with most qtranslate forks, and now, qTranslate-X as a merging point where all these come together, and most important: community based, opensource.
Keep up the good work guys :)
Alright! Then, if time permits, lets try to keep up the pace with your merge, and be compatible with you guys. WordPress 4.2 (April 2015) or 4.3 ( August 2015) seem to be a good target.
I might even pick up qtranslate-meta, the last of the trio!
also, that plugin also has a github repository which is always useful, to check their filters :D
Great, this is the git of the Multilanguage plugin. It looks like a fork of qTranslate also.
Could you guys do a favor to me and test the latest from GitHub https://github.com/qTranslate-Team/qtranslate-x version together with -slug? Especially category/tags/menu editors. There has been a lot of changes, both bug fixes and new features. I would appreciate very much if you could try to break it in any way you can imagine.
@johnclause and @LC43 One thing I've notested recently is that the widget is now duplicated. With mqTranslate, qtranslate-slug overrides the language chooser. Now, with qTranslate-X I have two widgets available, one from -X and other from -slug. Both have different options now, -slug have language code option and no final colon, and -x now have "hide title colon:" patch. At the moment I like most the qtranslate-slug one, I think the control of the title is simpler without the need of option to hide final colon(:). The option for locale code is also interesting as it can be a much more simpler text to be shown. One more time I must say that it would be great to just merge the slug options in main qTranslate-X to avoid this duplicate effort and keeping the -slug widget functionallity :)
Hello,
I am a new user to Qtranslate X and have implemented it for the first time on my personal travel blog. I'm a long time WPML user but the lack of permalink translation for CPT and Custom taxonomies and the cost made me search around a better solution.
After analyzing the localization WordPress plugin "market", I chose Qtranslate X because of its versatility and flexibility. However, I couldn't make the permalink translation work either. Czechs and frenchs urls are all the same but language folder prefix. So user are led to the right pages, there's no problem with that but I'd like to be it right.
After some research I found and installed Qtranslate Slug with much hope but it failed. It disabled pretty permalinks and displayed the ugly ones (with php parameters please). Also, permalink fields are now disabled in post and page edit page. Well, I can't work with that.
After searching the internet for some miracle, I found this discussion that seems abandoned for 18 months. I really want to see the merge happening so here are my questions :
Looking forward to hearing from you.
Cheers, Axel
Bump what's up with the direction of this project? I can't find any other URL tranlation tools for Wordpress, and I'm currently using QTranslate-X. However, QTS breaks my permalink structure completely, so it's not usable for me. Unfortunately we don't have the resources to redo the whole website internationalization after so much work with Qtranslate-X.
Any guidance will be appreciated, even if geared towards making the changes to the rewrite rules in-house and making a pull-request.
Hi everyone,
@johnclause has been working hard at qtranslate-x, and many of our features have been fixed in their code. Our broken menu changer has been fixed in his, apparently his widget has more features than ours, and the user interface seems to be pleasing to their users.
Not sure where mqtranslate is going, and if people altogether move to the common qtranslate-x code base, with slug capabilities ( not just slug for post, but for all taxonomies and CPT too), this plugin should be updated with only bug fixes so its compatible with older qtranslate and mtranslate.
Any thoughts on this?