Derby
  1. Derby
  2. DERBY-2186

Publicate Japanese translation of "Getting Started with Derby" on the web

    Details

      Description

      I found Japanese translated manual at
      http://db.apache.org/derby/docs/dev/ja_JP/getstart/ and
      http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html already.

      However, characters in former is broken and they are not publicated at the manual page.

      1. DERBY-2188.patch
        0.9 kB
        Tomohito Nakayama
      2. ja_JP.tar.gz
        68 kB
        Tomohito Nakayama

        Issue Links

          Activity

          Hide
          Tomohito Nakayama added a comment -

          DERBY-2188.patch is patch for site.

          ja_JP.tar.gz is Japanese translated manuals compiled at my environment.
          This is not corrupted.
          I don't know why current uploaded file have corrupted characters ....

          Show
          Tomohito Nakayama added a comment - DERBY-2188 .patch is patch for site. ja_JP.tar.gz is Japanese translated manuals compiled at my environment. This is not corrupted. I don't know why current uploaded file have corrupted characters ....
          Hide
          Tomohito Nakayama added a comment -

          I forgot PDF was broken...
          I think we need to wait till FOP supports Japanese ...

          Show
          Tomohito Nakayama added a comment - I forgot PDF was broken... I think we need to wait till FOP supports Japanese ...
          Hide
          Tomohito Nakayama added a comment -

          I want to make corrupted PDF as another issue from this.

          Show
          Tomohito Nakayama added a comment - I want to make corrupted PDF as another issue from this.
          Hide
          Jean T. Anderson added a comment -

          DERBY-2188.patch looks great – thanks! I went ahead and committed it, revision 487870, and did the 'svn up' on people.apache.org. It'll take about an hour for changes to become visible.

          Show
          Jean T. Anderson added a comment - DERBY-2188 .patch looks great – thanks! I went ahead and committed it, revision 487870, and did the 'svn up' on people.apache.org. It'll take about an hour for changes to become visible.
          Hide
          Andrew McIntyre added a comment -

          The files that are on the Apache server are not corrupt. I downloaded getstart-single.html from /www/db.apache.org/derby/docs/dev/ja_JP/getstart on people.apache.org using sftp and the file that I downloaded displayed properly and had no corrupted characters or question marks. The file served from http://db.apache.org/ does, so I believe that there is a misconfiguration of the Apache web server.

          I may be able to override it with a .htaccess file in the ja_JP directory. What is the encoding you used in the files? I tried UTF-8, which is what the DITA files have for their encoding in their <?xml encoding> value, but that didn't seem to work.

          Show
          Andrew McIntyre added a comment - The files that are on the Apache server are not corrupt. I downloaded getstart-single.html from /www/db.apache.org/derby/docs/dev/ja_JP/getstart on people.apache.org using sftp and the file that I downloaded displayed properly and had no corrupted characters or question marks. The file served from http://db.apache.org/ does, so I believe that there is a misconfiguration of the Apache web server. I may be able to override it with a .htaccess file in the ja_JP directory. What is the encoding you used in the files? I tried UTF-8, which is what the DITA files have for their encoding in their <?xml encoding> value, but that didn't seem to work.
          Hide
          Jean T. Anderson added a comment -

          Andrew, was it just the PDF that is corrupt? --The others appear to display just fine for me using firefox.

          Show
          Jean T. Anderson added a comment - Andrew, was it just the PDF that is corrupt? --The others appear to display just fine for me using firefox.
          Hide
          Jean T. Anderson added a comment -

          I take it back – /www/db.apache.org/derby/docs/dev/ja_JP/getstart is just less visibly corrupt on firefox; it's much more visibly corrupt on safari where the question marks are highlighted. I can't judge whether it's correct or not with internet explorer on windows. There aren't any question marks, but there are rectangles that might be suspicious.

          /www/db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html serves up correctly for me on firefox, safari, and internet explorer.

          Show
          Jean T. Anderson added a comment - I take it back – /www/db.apache.org/derby/docs/dev/ja_JP/getstart is just less visibly corrupt on firefox; it's much more visibly corrupt on safari where the question marks are highlighted. I can't judge whether it's correct or not with internet explorer on windows. There aren't any question marks, but there are rectangles that might be suspicious. /www/db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html serves up correctly for me on firefox, safari, and internet explorer.
          Hide
          Andrew McIntyre added a comment -

          And I take it back, there is corruption in the files of the multi-page HTML from my nightly doc build. I don't get the same corruption when building on my Mac. I will investigate and see if I can determine the source of the problem on my build machine. I don't see any errors reported during the build for the Japanese Getting Started manual.

          I could have sworn that the getstart-single.html also appeared corrupt earlier in my browser, but now it doesn't appear to be the case.

          As for configuring FOP to use Japanese fonts for the PDF, it should be possible, see:

          http://www.javaranch.com/journal/200409/CreatingMultipleLanguagePDFusingApacheFOP.html

          for a step-by-step tutorial. Integrating the extra arguments for FOP into the DITA build process may not be easy, but it should be possible.

          Show
          Andrew McIntyre added a comment - And I take it back, there is corruption in the files of the multi-page HTML from my nightly doc build. I don't get the same corruption when building on my Mac. I will investigate and see if I can determine the source of the problem on my build machine. I don't see any errors reported during the build for the Japanese Getting Started manual. I could have sworn that the getstart-single.html also appeared corrupt earlier in my browser, but now it doesn't appear to be the case. As for configuring FOP to use Japanese fonts for the PDF, it should be possible, see: http://www.javaranch.com/journal/200409/CreatingMultipleLanguagePDFusingApacheFOP.html for a step-by-step tutorial. Integrating the extra arguments for FOP into the DITA build process may not be easy, but it should be possible.
          Hide
          Tomohito Nakayama added a comment -

          Encoding in DITA file was UTF-8.

          I think first my description was not clear. Sorry.

          http://db.apache.org/derby/docs/dev/ja_JP/getstart/ is corrupted and
          http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html is not corrupted.

          // "Former" meant former in these 2 urls....

          Show
          Tomohito Nakayama added a comment - Encoding in DITA file was UTF-8. I think first my description was not clear. Sorry. http://db.apache.org/derby/docs/dev/ja_JP/getstart/ is corrupted and http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html is not corrupted. // "Former" meant former in these 2 urls....
          Hide
          Tomohito Nakayama added a comment -

          About FOP, there are problem of license for Font ...
          If we use not free font for PDF, it would be very difficult for developper to build it.

          Show
          Tomohito Nakayama added a comment - About FOP, there are problem of license for Font ... If we use not free font for PDF, it would be very difficult for developper to build it.
          Hide
          Tomohito Nakayama added a comment -

          And sorry for improper name for the patch.
          DERBY-2186.patch is proper ....

          Show
          Tomohito Nakayama added a comment - And sorry for improper name for the patch. DERBY-2186 .patch is proper ....
          Hide
          Tomohito Nakayama added a comment -

          By the way, I hope issue for Japanese PDF file is talked at DERBY-2187.
          // I think manual in HTML format should be available firstly on web in this issue.

          Show
          Tomohito Nakayama added a comment - By the way, I hope issue for Japanese PDF file is talked at DERBY-2187 . // I think manual in HTML format should be available firstly on web in this issue.
          Hide
          Andrew McIntyre added a comment -

          The problem I ran into was not with the license for the font, but the format of the font. FOP's TTFReader reported that the MS Gothic font in msgothic.ttc shipped with Windows did not have license restrictions, but rather the version of MS Gothic that I had was in Postscript Type 3 format, which FOP does not supported for embedding in PDF files.

          Of course, we could not check in the MS Gothic font, but it could be used by a someone building the docs to produce PDFs if the user has a valid Windows license. In an ideal situation, we would have a compatibly licensed Japanese font in Truetype or Postscript Type 1 format that we could embed into the Japanese PDF with FOP. Tomohito, you are probably the best person to find out if a font like that exists.

          I am still investigating the problem with the multiple-page HTML files. It builds fine on the Mac, but I get corruption in the individual HTML pages on Windows. The problem appears to be with Ant's <copy>/<move> tasks. The files that are transformed by the Xerces/Xalan in the DITA transform steps are correct. It is the copy in Ant to add the Apache license header that causes the corruption. I have not determined yet why this happens only on Windows and not also on the Mac.

          Show
          Andrew McIntyre added a comment - The problem I ran into was not with the license for the font, but the format of the font. FOP's TTFReader reported that the MS Gothic font in msgothic.ttc shipped with Windows did not have license restrictions, but rather the version of MS Gothic that I had was in Postscript Type 3 format, which FOP does not supported for embedding in PDF files. Of course, we could not check in the MS Gothic font, but it could be used by a someone building the docs to produce PDFs if the user has a valid Windows license. In an ideal situation, we would have a compatibly licensed Japanese font in Truetype or Postscript Type 1 format that we could embed into the Japanese PDF with FOP. Tomohito, you are probably the best person to find out if a font like that exists. I am still investigating the problem with the multiple-page HTML files. It builds fine on the Mac, but I get corruption in the individual HTML pages on Windows. The problem appears to be with Ant's <copy>/<move> tasks. The files that are transformed by the Xerces/Xalan in the DITA transform steps are correct. It is the copy in Ant to add the Apache license header that causes the corruption. I have not determined yet why this happens only on Windows and not also on the Mac.
          Hide
          Tomohito Nakayama added a comment -

          At my environment, I compiled multiple page HTML on Linux and found no problem...

          I will try font which I posted at http://issues.apache.org/jira/browse/DERBY-2187#action_12459123 .
          I hope it solves the problem.

          Show
          Tomohito Nakayama added a comment - At my environment, I compiled multiple page HTML on Linux and found no problem... I will try font which I posted at http://issues.apache.org/jira/browse/DERBY-2187#action_12459123 . I hope it solves the problem.

            People

            • Assignee:
              Unassigned
              Reporter:
              Tomohito Nakayama
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development