According to the CLDR documentation, we can specify a region overriding the region specified in the language identifier.

Does Globalize support this extension?

If yes, any help would be greatly appreciated.

I don't see a point of only uploading screenshots, or if there is one, having the option to only click "Upload and save" would be nice, as it has a much lower chance of accidentally not saving uploads.

We need to add docs for the new create_project command

How we do that is related to translate/pootle#6761

In fuent.js, we restricted the options to NUMBER and DATETIME beyond what's documented in the guide right now.

We should port those changes over.

The FluentBundle struct, although present in the introduction text of the documentation, is not actually documented. The link there to FluentBundle sends me here, but I see a 404:

![image](https://user-images.githubusercontent.com/9929737/78311944-31b1ff80-754a-11ea-8f4d-fda113993bc7.pn

I know the library is EOL, but could you add a warning to the README about dev-mode? so that people will turn it off in production?

I just discovered that one of our servers was experiencing periodic hangs due to threads blocked on re-reading the jar file every time a translation was needed. This might no longer be relevant in v3 -- I couldn't quite tell from the changelog -- but the server use

Please describe your issue

The only documentation for this package is Godoc and the README.md file from this repo. We need to write better docs, some tutorial and use case examples to make package adoption easier.

Is this a bug, an improvement, a proposal or something else? Describe it.

Improvement

What's the expected behaviour, the current behaviour and the steps to repro

prop2po (http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/prop2po.html) produces a completely different po than serge when processing properties files
More specifically the comments are treated differently
What .properties flavor is serge using (translate toolkit has these flavors: flex, java, mozilla, java-utf8, skype, gaia, strings)?
To be even more specific to be

This can help new contributors on joining the project and also to use to specifiy a test data that contain the majority of combination of cases that can create issues.
I think that we can use the WordPress files and do a light version with a glossary.

The idea is that ESLint could show warnings if a string is not translatable and provide autofixing to easily change the string into a tagged template literal.

ESLint prefer-template rule: https://github.com/eslint/eslint/blob/master/lib/rules/prefer-template.js
Codemod to replace concatenated strings by template literals: https://vramana.github.io/blog/2015/12/21/codemod-tutorial/