@dobbel It is really very easy.

Follow the instructions here to set up internationalization
https://quasar.dev/options/app-internationalization

Sign up to the Localazy service to get your application keys

Add the localazy.json file to the root of your app with content like this:

{

  "writeKey": "[your write key]",
  "readKey": "[your read key]",
  
  "upload": {  
    "type": "js",
    "files": "src/i18n/en-us/index.js"
  },
  
  "download": {
    "files": "src/i18n/${lang}/index.js"
  }
  
}

(this is based on the folders created with the default i18n installation)

then use the commands:

localazy upload

check your translations and

localazy download

It is as simple as that.

I had some problems with the most recent upgrade - an error required me to delete the node_modules and .quasar folders and run npm install and quasar upgrade -i again.

All good so far, but there was a compile error which I am writing about here because I am sure it will catch others out.

The error was

SassError: semicolons aren't allowed in the indented syntax.

It turns out I had to remove the semicolons around my predefined colours in the quasar.variables.sass file.

After that everything was back to normal.

@ssuess That is just what I needed…thank you!

Is there any way to have more than 1 file containing translations strings for each language?

At the moment I have 1 index.js file for each translation, but I would like to break these into smaller files to separate, for example, strings that never change (like country names) with those that are more likely to change due to changes in the interface, resulting in having both an index.js and static.js file for each language.

Is that possible?

@metalsadman I am blocking more than 1 tab ahead, but I was hoping to use validation to stop progress, but it is only working for some fields and not others.

I have a large q-form around a stepper component, and when I make a validate() call, only some of the dynamically created fields which require input are flagged. All of the fields are custom variations of q-input or q-select, but I cannot work out why some of these correctly display as being required, when others do not.

If you tab through each the components, all works as expected, but if you jump to the next step of the process without tabbing, the user is not alerted of required content.

So I need to simulate a focus event on all of the components of a step to get this to work. Any suggestions how I could go about this or are there other ways to work around this?

The authors came back and said that this behaviour was expected, and that the inclusion of the quotes makes no difference to the outcome, which may be right, but it does add to the payload and reduces readability so I will suggest that they include this as an option in the future.

Now I have to find out how I can have multiple language files for each language, so I can have dynamic translations that need to be maintained by this program, and static translations (for things like country names) which do no change. Any ideas how I can have more that 1 js file in each language folder?

Actually I found a small issue with the output (the output files have quotes around the key values, even though they are not present in the source) and so I have asked the developers for clarification on how to resolve this.

Apart from that, i think this is a brilliant idea, very well executed.

@dobbel It is really very easy.

Follow the instructions here to set up internationalization
https://quasar.dev/options/app-internationalization

Sign up to the Localazy service to get your application keys

Add the localazy.json file to the root of your app with content like this:

{

  "writeKey": "[your write key]",
  "readKey": "[your read key]",
  
  "upload": {  
    "type": "js",
    "files": "src/i18n/en-us/index.js"
  },
  
  "download": {
    "files": "src/i18n/${lang}/index.js"
  }
  
}

(this is based on the folders created with the default i18n installation)

then use the commands:

localazy upload

check your translations and

localazy download

It is as simple as that.

I have answered my own question: all that was required was to use the file type js instead of json and it works beautifully.

Nice stuff!

I saw a demo of Localazy here: https://vaclavhodek.com/how-to-localize-vuejs-app-with-vue-i18n-and-localazy and I LOVE the idea of outsourcing my localisation via an online portal so I thought I would check it out.

I got everything working to a point, and before I contact Localazy - has anyone got their library working? From what I can see it is expecting a straight js file and so:

{
  "helloworld": "Hello World!"
}

works but the default format for a quasar language file:

export default {
  helloworld: "Hello World!"
}

Does not, and neither does the export have the correct header. I can use intermediate files of course (which is what I am doing for testing) but is there a more elegant way?