Hi Josh I have the same problem, and I don't agree that the best fix will be "to use correct file extensions".
I believe Google Translate should use the *content-type* http header to identify the type of file. For example: what is the "extension" of http://translate.google.es/, of course none, it has no extension, but the server adds a response header (HTTP header, not HTML) that says: Content-Type:text/html; charset=UTF-8 Clients can decide with parser to use when rendering the content. Thanks, Javier -- You received this message because you are subscribed to the Google Groups "General" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-translate-general/-/KvxVNAyvK_EJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-translate-general?hl=en.
