Skip to content

Conversation

@gaearon
Copy link
Member

@gaearon gaearon commented Aug 31, 2018

I think it's unacceptable to have Google Translate broken on our website, especially considering we don't yet offer any official translations. See facebook/react#12460.

So I'm adding a hack described in facebook/react#11538 (comment). I'm not too worried about performance since this is mostly a static website anyway.

Before the hack:

After the hack:

@reactjs-bot
Copy link

reactjs-bot commented Aug 31, 2018

Deploy preview for reactjs failed.

Built with commit d72a2c7

https://app.netlify.com/sites/reactjs/deploys/5b888aa682d3f124a5d5bd7e

@gaearon
Copy link
Member Author

gaearon commented Aug 31, 2018

cc @KyleAMathews dunno if you get questions about this but you might find it useful.. just don't make it a default.

@KyleAMathews
Copy link
Contributor

Yeah, there's been one issue about it gatsbyjs/gatsby#6300

Pointed people there here.

Copy link
Contributor

@bvaughn bvaughn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

itrustyou

@gaearon
Copy link
Member Author

gaearon commented Aug 31, 2018

I think gatsbyjs/gatsby#6300 is different and is about #467. We need to fix it too. Can you help? I’m not sure where to look.

@KyleAMathews
Copy link
Contributor

@gaearon yeah — I'm pretty sure we could support it when some other tool mutates the URL assuming the patterns are consistent. I'm tied up currently getting Gatsby v2 out but I'd be happy to support someone who wants to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants