Menu
▾
▴
gnuplot-beta
|
From: Shigeharu T. <sh...@ie...> - 2006-03-20 08:05:12
|
shige 03/20 2006 ---------------- Thanks for kindly advices. I will submit our translations to sourceforge site. Well, I want to submit the following files: A: the Japanese translation of gnuplot.doc ((1) [a]) B: a patch for Japanese translations of term/*.trm ((1) [b]) C: README for Japanese user ((1) [c]) D: .pdf format file made from A ((4)) E: the Japanese translation of faq/faq.tex ((5)) F: .pdf format file made from E ((6)) G: the Japanese translation of wgnuplot.mnu ((7) [f]) H: wgnuplot.hlp made from A ((7) [g]) I: README for Japanese MS-Windows user ((7) [h]) Files D,F,H are not ASCII text files. However, http://sourceforge.net/docman/new.php?group_id=2055 says: Documents submitted here may consist of either normal ASCII text, or text with HTML mark-up. Documentation in other formats will not be processed -- all documentation should be either normal ASCII text or text with HTML mark-up. Can I submit them there ? If not, where should I submit them ? +========================================================+ Shigeharu TAKENO NIigata Institute of Technology kashiwazaki,Niigata 945-1195 JAPAN sh...@ie... TEL(&FAX): +81-257-22-8161 +========================================================+ |
|
From:
<br...@ph...> - 2006-03-20 14:56:31
|
Shigeharu TAKENO wrote: > Thanks for kindly advices. I will submit our translations to > sourceforge site. Submissions to the web site are of secondary interest only. The key parts will be submissions to the source CVS tarball. > Well, I want to submit the following files: > > A: the Japanese translation of gnuplot.doc ((1) [a]) > B: a patch for Japanese translations of term/*.trm ((1) [b]) > C: README for Japanese user ((1) [c]) > D: .pdf format file made from A ((4)) > E: the Japanese translation of faq/faq.tex ((5)) > F: .pdf format file made from E ((6)) > G: the Japanese translation of wgnuplot.mnu ((7) [f]) > H: wgnuplot.hlp made from A ((7) [g]) > I: README for Japanese MS-Windows user ((7) [h]) > > Files D,F,H are not ASCII text files. However, A,B,C,E,G and I should go into the CVS. The generated files (D,F,H) can then be published where you like. > http://sourceforge.net/docman/new.php?group_id=2055 gnuplot hasn't ever used SF.net's "Documentation Manager" so far. I don't think this is the point to start. If at all, only HTML editions of the documentation ("make html" in docs) and FAQ really would make sense there. |
|
From: Ethan M. <merritt@u.washington.edu> - 2006-03-20 19:53:20
|
On Monday 20 March 2006 06:56 am, Hans-Bernhard Br=F6ker wrote:
> Shigeharu TAKENO wrote:
> > Well, I want to submit the following files:
> >
> > A: the Japanese translation of gnuplot.doc ((1) [a])
> > B: a patch for Japanese translations of term/*.trm ((1) [b])
> > C: README for Japanese user ((1) [c])
> > D: .pdf format file made from A ((4))
> > E: the Japanese translation of faq/faq.tex ((5))
> > F: .pdf format file made from E ((6))
> > G: the Japanese translation of wgnuplot.mnu ((7) [f])
> > H: wgnuplot.hlp made from A ((7) [g])
> > I: README for Japanese MS-Windows user ((7) [h])
> >
> > Files D,F,H are not ASCII text files. However,
>
> A,B,C,E,G and I should go into the CVS. The generated files (D,F,H) can
> then be published where you like.
Should we create a new directory at the top level of the tree?
.../japanese/all_Shige's_files
Otherwise the individual pieces could go in their respective existing
directories, but that seems confusing to me.
.../docs/japanese/
.../term/japanese/xxx.patch
.../? (currently the FAQ is in a separate cvs tree)
Shige: =20
Will your README file explain how to apply the terminal patches,
and anything else necessary to prepare the cvs source tree for
building a Japanese version from source?
|
|
From: Shigeharu T. <sh...@ie...> - 2006-03-22 09:09:15
|
shige 03/22 2006
----------------
Hans-Bernhard_Br wrote:
> Submissions to the web site are of secondary interest only. The key
> parts will be submissions to the source CVS tarball.
O.K. Well, where should I submit them ? "Docs" section, or
"Patches" section ? I will modify translations along with changes
of original documents, so I will submit them sometimes.
> A,B,C,E,G and I should go into the CVS. The generated files (D,F,H) can
> then be published where you like.
O.K. I will open the pdf files (D,F) on my Web site if I need.
Ethan Merritt wrote:
> Will your README file explain how to apply the terminal patches,
> and anything else necessary to prepare the cvs source tree for
> building a Japanese version from source?
O.K. I will write them to the README. I will also explain the way
to make pdf files (it is not only "make pdf" because pdflatex
command does not parse the Japanese LaTeX file).
Since it is more complicated to make Japanese wgnuplot.hlp (H),
I hope H will be included in the directory.
+========================================================+
Shigeharu TAKENO NIigata Institute of Technology
kashiwazaki,Niigata 945-1195 JAPAN
sh...@ie... TEL(&FAX): +81-257-22-8161
+========================================================+
|
|
From:
<br...@ph...> - 2006-03-24 15:25:11
|
Shigeharu TAKENO wrote: > O.K. Well, where should I submit them ? "Docs" section, or > "Patches" section ? The general idea is you become a gnuplot team member and check them into CVS yourself, so you can also update them on your own schedule, without our help. Failing that, zip them up and post the package to the 'Patches' tracker. > Since it is more complicated to make Japanese wgnuplot.hlp (H), > I hope H will be included in the directory. I really would like to avoid it. How is making the Japanese version of wgnuplot.hlp more complicated than the normal one? |
|
From: Shigeharu T. <sh...@ie...> - 2006-03-25 12:14:22
|
shige 03/25 2006 ---------------- Hans-Bernhard Brr wrote: | The general idea is you become a gnuplot team member and check them into | CVS yourself, so you can also update them on your own schedule, without | our help. Failing that, zip them up and post the package to the | 'Patches' tracker. O.K. I will post gzip files to 'Patches' section. I will send A, B,C,G and I in this time. A: gnuplot-ja.doc.gz B: term-ja.diff.gz C: README.ja.gz G: wgnuplot-ja.mnu.gz I: README.win-ja.gz | I really would like to avoid it. How is making the Japanese version of | wgnuplot.hlp more complicated than the normal one? The Japanese RTF file is not make correctly by "make rtf", so we have to do as the followings: % cd docs % patch -p1 < ../../doc2rtf-38j0.diff % make clean % make 'CFLAGS=-g -O2 -DJAPANESE -DALL_TERM_DOC' doc2rtf % gcc -o testrtf1 ../../testrtf1.c % ./doc2rtf gnuplot-ja.doc tmpf % nkf -s -Lw tmpf | ./testrtf1 > gnuplot-ja.rtf where doc2rtf-38j0.diff and testrtf1.c are for encoding of the Japanese (8bit) RTF file which are available as http://takeno.iee.niit.ac.jp/~foo/gp-jman/data/doc2rtf-38j0.diff http://takeno.iee.niit.ac.jp/~foo/gp-jman/data/testrtf1.c and nkf is the standard Japanese encoding filter from EUC-JP (using Japanese Unix) to Shift_JIS (using Japanese MS-Windows). For making other format files like LaTeX, PDF, we also need some additional instructions, or do another way for the Japanese document. +========================================================+ Shigeharu TAKENO NIigata Institute of Technology kashiwazaki,Niigata 945-1195 JAPAN sh...@ie... TEL(&FAX): +81-257-22-8161 +========================================================+ |
|
From:
<br...@ph...> - 2006-03-24 18:01:15
|
Ethan Merritt wrote: > Should we create a new directory at the top level of the tree? > .../japanese/all_Shige's_files If they come as a "how to change the source code into that of Japanese gnuplot": yes. Deviating from that scheme, those files that just replace existing files in that process could be installed next to those, e.g. docs\japanese.doc src\win\japanese.mnu and so on. I don't think there's any point in creating a subdirectory for a single file. |
