Martin, I was thinking that you can copy and paste from the browser to get to the translated text. At any rate...I wonder if we can use the Google or Bing API to translate the Static HTML pages. Pass in the French page and get back the English programmatically?
I may investigate this as I know it's possible to do with some translation software applications. Adam > On Aug 6, 2014, at 5:13 AM, Martin Desruisseaux <[email protected]> > wrote: > > Hello Adam > > The Google translation looks better than I expected. It could be used as > a starting point for the text content. But I had a look at the HTML code > and saw a lot of code inserted by Google: a very large amount of > JavaScript, new tags like <span class="notranslate" onmouseover="...">, > all URL modified to redirect to Google translate, etc. If we were using > that HTML code, the effort of cleaning it may be large. > > I had a look for some editors (Notepad++, Atom, Mou). If Christina is on > Windows, maybe the easiest one would be Notepad++ > (http://notepad-plus-plus.org). Would it be possible to do the following > in order to evaluate if this approach would work? > > * Create a new directory anywhere. > * Go to https://svn.apache.org/repos/asf/sis/site/trunk/content/book/ > , right-click on book.css, choose "Save link as" or "Save target as" > (depending on the browser), save the file in the new directory. > * Creates a "en" sub-directory. > * Go to > https://svn.apache.org/repos/asf/sis/site/trunk/content/book/fr/ , > right-click on developer-guide.html, choose "Save link as" or "Save > target as", save in the "en" sub-directory. > * Download and install http://notepad-plus-plus.org (Windows only) > * Open the <new directory>/en/developer-guide.html file using Notepad++ > > > Hopefully, Notepad++ would apply syntax coloration. Would it be okay to > edit the text in-place while ignoring all the HTML tags? Hopefully the > syntax coloration would make easier to distinguish the text from the tags. > > The table of content can be ignored because it can be automatically > generated. Line length doesn't matter much - I tend to use one line per > sentence, or to split after comma if the sentence is long, in order to > get simpler diff on SubVersion if we later re-edit or move around some > sentences. > > > Martin > > > > Le 05/08/14 21:42, Adam Estrada a écrit : >> Here's the non-Apache shortened link. >> >> http://goo.gl/GFa1O3 >> >> Adam >> >>> On Tue, Aug 5, 2014 at 3:40 PM, Adam Estrada <[email protected]> wrote: >>> Martin, >>> >>> I don't know of a good text editor. Just curious...how does Google >>> Translate do on this documentation? >>> >>> http://s.apache.org/ubj7 >>> >>> At first glance, it appears to do an OK job. The problem is that it >>> doesn't translate the whole page. I'm really just testing around with >>> this today so no big deal... >>> >>> Adam >
