Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Chatwoot
  3. Individual translations for Chatwoot

Individual translations for Chatwoot

Scheduled Pinned Locked Moved Chatwoot
4 Posts 2 Posters 867 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jan.reinhardtJ Offline
      jan.reinhardtJ Offline
      jan.reinhardt
      wrote on last edited by girish
      #1

      Hi everybody. I'd like to change some of the standard texts defined in /app/code/app/javascript/widget/i18n/de.json but this file is write protected. Is there any option to move the language file(s) to a different location where it a) can be changed as desired and b) are not overwritten in case of package updates?

      girishG 1 Reply Last reply
      0
      • jan.reinhardtJ jan.reinhardt

        Hi everybody. I'd like to change some of the standard texts defined in /app/code/app/javascript/widget/i18n/de.json but this file is write protected. Is there any option to move the language file(s) to a different location where it a) can be changed as desired and b) are not overwritten in case of package updates?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @jan-reinhardt I think it's best if the upstream project is updated with the translations first. The upstream project uses crowdin. See https://github.com/chatwoot/chatwoot#translation-process

        jan.reinhardtJ 1 Reply Last reply
        0
        • girishG girish

          @jan-reinhardt I think it's best if the upstream project is updated with the translations first. The upstream project uses crowdin. See https://github.com/chatwoot/chatwoot#translation-process

          jan.reinhardtJ Offline
          jan.reinhardtJ Offline
          jan.reinhardt
          wrote on last edited by
          #3

          @girish Yes I know and I read that, but in this case its not about creating new translations. The existing translations are correct and I'd just like to change the wording in some cases because they don't fit my use case.

          girishG 1 Reply Last reply
          1
          • jan.reinhardtJ jan.reinhardt

            @girish Yes I know and I read that, but in this case its not about creating new translations. The existing translations are correct and I'd just like to change the wording in some cases because they don't fit my use case.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            @jan-reinhardt that would be difficult for us to maintain. I think best approach is to fork the existing package and create a custom build. Code is at https://git.cloudron.io/cloudron/chatwoot-app

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search