Is there a forecast for multi-language support?

[chinno...@gmail.com]

Many messages can be changed without difficulties, however we have to change .JS files that is not good, so an idea for some file that has all the default message in English, needing only to duplicate this file for other languages and inform in the API config.

So, I'm changing the files in the files, because I need to speak Portuguese for the client, but some I'm not finding, I believe it's coming from QZ Tray, how to proceed in this case since some are dynamic?

Eg:
- A printer must be specified before printing
- Cannot find printer with name "asdfg"

Where are these messages coming from?

[Tres Finocchiaro]

Language support is not slated for a release.  We're currently focusing on bugs and features.

We do invite anyone from the community to assist with this effort (i18n, etc).

If it's not started by 2.3, we'll be milestoning it, but this would be at least a year out.

One recommendation is to catch and re-throw the most common errors in Portuguese... 

For example:

https://github.com/qzind/tray/blob/2.0/src/qz/printer/PrintOutput.java#L26

        if (configPrinter.has("name")) {
            service = PrintServiceMatcher.matchService(configPrinter.getString("name"));
            if (service == null) {
                throw new IllegalArgumentException("Cannot find printer with name \"" + configPrinter.getString("name") + "\"");
            }
        }

You could have a JavaScript utility which wrapped the errors in Portuguese until localization is implemented.

This is not ideal, but should be relatively safe for the 2.0 branch.

-Tres

 

- Tres.Fin...@gmail.com

--
You received this message because you are subscribed to the Google Groups "qz-print" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qz-print+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[chinno...@gmail.com]

I understand, I created a palette via javascript, intercepting these messages that comes straight from Java, for now resolved, when I spend some time here I see what I can contribute to this implementation.