pkernstock My two cents, if you don't mind:

Of course not, all feedback is welcome 🙂

pkernstock some integration of Discussion Language would make sense here

I do plan to integrate with fof/discussion-language in the new year actually. 👍

pkernstock For example to determine the current language - as it doesn't make sense to translate a English-tagged post into English, and also hide hide the option if it's the same language.

Did you run the detect command (php flarum translate:detect) after enabling the extension? 🤔 For posts where the language has been detected by the extension, the option to translate to the same language is removed already.. If the language is not detected (even if marked by discussion-language), then all languages (as dictated by the current permissions) are offered.

New posts created whilst the extension is active will be detected automatically.

The easiest way to tell if the extension has detected the language is by spotting the language header at the top of the post, like this:
image

    IanM Did you run the detect command

    Oh! Apologies. I've successfully over-read that part in late night hours installing this extension. I'm now running the command, and it takes a while. Thanks!

      pkernstock no problem. Yes, it can take a while to run the detection, if you have a large number of existing posts. Thankfully this is a one time process

        @IanM, greetings. Awesome extension!
        What does a license mean for non -commercial use and how much will one-time license cost for a commercial? Thanks

          18 days later

          IanM how well does this play with SEO? Do the cached translation turn into SEO juice as in if a post is in English and then cached and translated into Spanish for example, can Google see the Spanish translation of the post?

          Also, does this translate Primary and secondary tags?

          • IanM replied to this.

            Syirrus how well does this play with SEO? Do the cached translation turn into SEO juice as in if a post is in English and then cached and translated into Spanish for example, can Google see the Spanish translation of the post?

            There's currently no integration with SEO directly

            Syirrus Also, does this translate Primary and secondary tags?

            No, this extension focuses on the translation of user content only. Localizd by @glowingblue is the only extension I'm aware of to offer tag translations

              IanM Thank you for responding to my questions 🙂. In your opinion, is your plug pretty stable? It looks like an awesome plugin I'm thinking about picking up.

              • IanM replied to this.

                Syirrus yes, on the whole the extension is pretty stable and is in use on a few production sites.

                There is currently an issue with increased latency when the DeepL driver is in use, which I plan to release an update to address soon. The current workaround is to use either the Google Translate or Google Cloud Translate drivers, which do not cause this issue.

                  IanM Im not lucky, I missed this promotion.. hope this deal come again in Christmas..

                    kebindong IanM

                    I just picked up this extension and it’s great! It’s very clean and seamlessly works as well so far with my limited testing. It’s there, but you don’t notice it unless you need it. Thank and well done for sure!!!

                    I wish it had tag translation support and translation support for Titles, but it’s more important to translate the comments and posts.

                    Thank you again for this awesome extension!

                    I noticed there is a tag based permission issue when it comes to NOT being able to grant or restrict access based on "tags" access to the translate plugin based on tag.

                    You cannot click on or rather set any permissions based on tags.

                    IMAGE

                    • IanM replied to this.
                      11 days later

                      IanM

                      How much would it cost to implement a few additional features into your translate plugin?

                      1. The ability to translate the subject.
                      2. The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?
                        Bonus: the ability to localize tags.
                      • IanM replied to this.

                        Syirrus I noticed there is a tag based permission issue when it comes to NOT being able to grant or restrict access based on "tags" access to the translate plugin based on tag.

                        You cannot click on or rather set any permissions based on tags.

                        This is correct. The permissions to translate content is forum wide, rather than scoped for tags.

                        Syirrus The ability to translate the subject.

                        I am planning to introduce this feature soon 🙂

                        Syirrus The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?

                        I'm not sure I understand what you mean here?

                        Syirrus Bonus: the ability to localize tags.

                        Translation of tag display names is out of scope for this extension. Localizd by @glowingblue offers this functionality if you need it

                          IanM

                          IanM This is correct. The permissions to translate content is forum wide, rather than scoped for tags.

                          I understand.

                          IanM The ability to translate the subject.

                          Right on! That would be awesome if it's a easy change.

                          IanM The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?

                          I was thinking something that showed the following:

                          TITLE
                          There is the original text in English.

                          TRANSLATED TITLE
                          Here would be the text in another language

                          TRANSLATED TITLE
                          And yet more text in another language

                          These boxes (not coding text boxes) would be collapsable in CSS (collapsed by default) with the subject being translated title. So you wouldn't see the translated text below.

                          If someone wanted to see the translations, they could click translated "title" and see the whole translation. This would also make it so these translations would be picked up by Google.

                          Does that make sense?

                          IanM Translation of tag display names is out of scope for this extension. Localizd by @glowingblue offers this functionality if you need it

                          Yes, the price for that extension is prohibited, making it not an option for my project.

                          Syirrus

                          kebindong It's not only for admins. Depending on the permissions and user language localization normal users can translate posts.

                            Syirrus Thank you.
                            for testing, I set permissions of View translation in current locale to Everyone, and View translation in any forum locale to Members. and log in a testing role in my same device. But the testing role cannot see the translate dropdown menu in post. and my admin role can use it only. Im not sure which parts wrong.

                            Can I see your site if you dont mind..

                            thanks

                              kebindong Were you able to solve this? My forum site is still in testing and I'm not quite ready to share just yet. Do you have the user locale set when the log in, because if the users locale is set to the language the text is in, you won't see the translate button.

                                @IanM
                                I'm unable to update to 1.6.3 (minor update) because of the translate package.
                                I get the following error:

                                
                                  Problem 1
                                    - Root composer.json requires ianm/translate ^0.2.1, found ianm/translate[0.2.1] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.```
                                
                                Is there a way to resolve this?
                                • IanM replied to this.