react translations

think about how we can handle something like:

    Нажмите <a onClick={this.handleClick}>здесь</a>.

maybe this can be an option

<translate>
    Нажмите <a onClick={this.handleClick}>здесь</a>.
</translate>

extracted result

msgid "Нажмите <to>здесь<tc>"
msgstr ""

Example 2

Осталось: <span>{this.props.complainTextSymbolsLeft}</span>
                    {ungettext([' символ', ' символа', ' символов'], this.props.complainTextSymbolsLeft)}.

to - tag open tc - tag close

[MrOrz]

Whoa that was fast! I am currently on a trip with limited Internet connections, still catching up with rt. If React dependency is required inevitably, I agree with the idea that it should be in a separate npm package.

[AlexMost]

I have ended with something working here - https://jsfiddle.net/69z2wepo/72888/. Basically, we have rt tag, that can extract proper msgid and resolve translations from msgid with tags.

Good part

It works)

Bad part

To be able to place translated strings inside react component, I need to modify read only props.children somehow. I couldn’t find any appropriate solution for that and used React.cloneElement(). This adds react as a dependency to the whole lib. This one is a bad thing, and I am thinking about moving React support to some kind of extension of c-3po. What do you think guys @MrOrz @alxpy ?