My personal opinion: such ad-hoc configuration may slow down the system performance and over-complicate the 99.9% usage unnecessarily.
we can do this to HTML because it is standardized and it is common on the Internet. @Ptr nice idea, commonly used in industry, but it is hard for natural languages. On Aug 26, 6:51 pm, Ptr wrote: > The same problems arise for the usecase described here: > > http://groups.google.com/group/google-translate-general/browse_thread... > > It would be nice if there would be a parameter to force google > translate to ignore unknown terms. > > Regards, > Peter. > > On 25 Aug., 19:08, Zio wrote: > > > > > > I don't think we can fit such ad-hoc feature into the general purpose > > > translation framework. > > > A better solution might be provided by 3rd party developer who use > > > Google Translate API > > > But, how solution might be provided with the API if translator > > (through API too) brokes tags? I see only way to preparse document, > > strip all tags, then call API for translating clean text and after > > that - reapply all source tags to translation. IMHO - it is a bad way. > > > If html documents are supported now in general use, why it is > > excessive feature to translate other formatted text? (Not only TeX, > > but PHP, etc... sources) Problem only to NOT CHANGE special tags. -- You received this message because you are subscribed to the Google Groups "General" group. 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.
