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

The doc on https://moment.github.io/luxon/docs/class/src/interval.js~Interval.html states that:

To convert the Interval into other representations, see toString, toISO, toISODate, toISOTime, toFormat, and toDuration.

However, the link to toFormat() goes to the DateTime documentation page (it took me a while to realize this), and that page says:

You may not want this. See toLocaleStr

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.

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

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.

As documented in #80 there are several files that have to be included in a specific order. You also have to download the git submodule and include those files as well.

It would be really helpful if there was a distributed bundle that was created that continued a single, minified file with the entire library in it that was ready to load.

Webpack could be used to gen

How about replacing the magic file at app/utils/intl/missing-message.js with a hook on the service?

Something like this:

// ember-intl service
// …
missingTranslation(locale, key, options = {}) {
  return `Missing translation for ${key} in ${locale}`;
}

// …

That hook could be used both to modify the returned message, e.g. by hooking up a fallback message in a specifi

It would be great if this plug-in had the ability to catch internal links in MD/MDX files and turn them into multi-language routes similar to how Gatsby's gatsby-plugin-catch-links plugin does this.

Description

There are indeed a lot of fun things I myself experienced and some really driving me crazy because of the inconsistent implementation on different browsers including all old and modern browsers. If one implemented anything that does not follow the specs and happened to ship it to stable release in the browser, the bug is there forever as not all users will upgrade to the latest ve

Gives error on install. Seems to be related to the title and this thread:

zaach/jsonlint#103

It would be a nice addition to the README to document which major browsers are known to lack the support that this polyfill adds

• Main README should contain sections:
  • Features - what the lib is for
  • Installation
  • Getting started
  • Guides
    • How to implement own validations
    • Integration to redux-form
    • Integration to formik
  • Contribution
  • Link to API
• Every package should contain link to main page to our repo.