Index:

• formatXMLElementFn -- a function handling rich text formatting, passed to values. Name is used as referred in source code,

The problem

While using RichText, formatXMLElementFn are called with possible many arguments (chunks) which could be collected with rest operator and passed to component.

Example

<FormatMessage
  defaultMessage="This is <i>example

vue & vue-i18n version

8.15.4

Steps to reproduce

add missing handler:

i18n.missing = (locale: Locale, key: Path) => {
if (i18n.te(key, i18n.fallbackLocale)) {
return i18n.t(key, i18n.fallbackLocale).toString();
}

return ''; // instead of showing the key + warning
};

What is Expected?

no warnings about missing key

What is actually happening?

console

🚀 Feature Proposal

babel-plugin-fbt allows developers to use an attribute common to FBT calls which use JSX syntax. However, no documentation exists on https://facebookincubator.github.io/fbt/ for this feature.

Motivation

It is not clear how or why to use the common string API.

Example

This feature would allow organizations or developers to define a set of frequently

Describe the bug

This is an issue I encountered while migrating from the 3.0.0-5 version to 3.0.0-11. I probably have to use make-plural somewhere in my app, but I don't know where because the migration docs didn't mention it.

To Reproduce

Steps to reproduce the behavior, possibly with minimal code sample, e.g:

import { plural } from '@lingui/macro'
import { useL

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.

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/91359822-also-save-uploaded-screenshots?utm_campaign=plugin&utm_content=tracker

Is your feature request related to a problem? Please describe.
in other translation platforms you need to import only template file, after that you can translate all strings from it to other languages. But in traduora i can't do that. Do you plan to add this feature, or how to do workflow? Template file create automatic via extracting strings from source code.
When i'm use zanata i'm upload

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 am trying to migrate old database from another framework into django and currently, I am having trouble saving the newly generated models. I get an error when I do the following:

title_translated = create_translated_data(r[4])
content_translated = create_translated_data(r[3])
new_post = Post.objects.create() # <-- This is where I get my error.

t = {}

for loc, data in title_transl

If I use react-localize-redux with typescript I will encounter type issue when passing the value to the 'translate' function and expecting to use returned string as a placeholder text for input form element.

Typescript is complaining that return value wont be a string but this instead:

![image](https://user-images.githubusercontent.com/4181978/64955411-76b16580-d888-11e9-8216-2fa03696c587

An error will occur if a document is added to the automatic sitemap but has no URL/path format. (See traceback below). This can be avoiding by checking for doc.path_format before accessing the url property on the Document object.

(Basically, the list of docs should filter out Document objects that don't have a path_format).

[20:38:10] Error building <grow.rendering.render_cont

When I generate HTML on OSX then 150 is displayed as €150.00.

When doing the same on Fedora 150 is just €150.

Any idea what might be the problem???

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