taskSavannah Administration - Tasks: task #6504, Submission of CJK-LaTeX


task #6504: Submission of CJK-LaTeX

Submitted by:  Werner LEMBERG <wl>
Submitted on:  Sat 10 Feb 2007 03:11:35 PM UTC  
Should Start On:  Fri 09 Feb 2007 11:00:00 PM UTC Should be Finished on:  Mon 19 Feb 2007 11:00:00 PM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Sylvain Beucler <Beuc>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Fri 06 Apr 2007 10:01:21 PM UTC, comment #3: 

> > > Folks, may I ask again whether it's possible, similar to GNU
> > > lilypond, to use git for my project?  Can you activate it?
> >
> > Git doesn't have a proper integration and automation through Savane,
> > so we essentially are testing it. If you acknowledge the "beta"
> > status and provide feedback, there's no problem with activating a
> > git repo for your project.
> This is fine with me!  LilyPond's git repository works just fine; the
> only thing I'll then need is to write a script to get snapshot
> tarballs once or twice a day (or after a change).

That sounds ressource-intensive. We replaced CVS tarballs with anonymous rsync access because of that. I'm not sure that's a good idea.

> > Afaics Sebastian is waiting for a version of your project with
> > proper notices, suitable for public release at Savannah.  From your
> > answer in the future ("I will") I can't determine whether your
> > tarball has that or not, maybe you can clarify :) For now the
> > project is still in "pending" mode.
> Ah, ok.  Well, I've replied that as the maintainer of GNU troff, I
> believe that you can trust me to do that as soon as the git repository
> is in place.

Well there was several cases of GNU projects submitted at Savannah that had missing or outdated notices :/ Thus that sounded like a nice opportunity not to check the source code, but alas we have to check even for those.

Looking at groff, the notices look fine :)

> I would like to continue the repository without any
> intermediate changes.  In case this isn't possible, please tell me.
> Otherwise, I ask you to import the CVS; within the next days I would
> add the missing copyright notices.

Ok I approved your project.

Sylvain Beucler <Beuc>In charge of this item.
Sun 11 Mar 2007 11:46:56 PM UTC, comment #2: 

I'll of course add copyright notices.

I won't use GNU FDL.

Everything in the CJK bundle is GPLed, in the public
domain, or using a license compatible to the GPL,
including the stuff in the `utils' directory.

A clean bundle can be found here:


this file is also on CTAN.

Werner LEMBERG <wl>
Sun 11 Mar 2007 06:16:53 PM UTC, comment #1: 

I'm evaluating the project you submitted for approval in Savannah.

At first, in order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the beginning of every file of source code.

In addition, if you haven't already, please include a copy of the plain text version of the GPL,
available from http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.
To learn why a copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.

At second, to release your documentation under the terms of the GNU FDL, please follow these instructions:
In order to release your project properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING' (http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.

At third, can you please list the utils you include in your tarball with their licenses? It is important for us to check if they are released under a GPL compatible license.

At fourth, please send us a "clean" tarball instaed of a tared CVS source directory. It is hard to read the ",v" files at all.
I would lile to have a look at your whole complete files, and not just look at the diff(erence)s.


Sebastian Wieseler <kickino>
Project Member
Sat 10 Feb 2007 03:11:35 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.

Registration Administration

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):

Registration Details

  • Name: CJK-LaTeX
  • System Name:  cjk
  • Type: non-GNU software & documentation
  • License: GNU General Public License V2 or later


CJK, a LaTeX2e macro package which enables the use of CJK scripts
(Chinese/Japanese/Korean) in various encodings.

The current CVS is no longer working due to a hard disk crash;
additionally, the ffii.org people are no longer willing to host
my project for various reasons.

Here's a pointer to the complete CVS archive instead:


Other Software Required:


Other Comments:

I would like to use git, not CVS.

Werner LEMBERG <wl>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by kickino (Posted a comment)
  • -email is unavailable- added by wl (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-04-06 Beuc StatusWait reply => Done
        Assigned tokickino => Beuc
        Open/ClosedOpen => Closed
    2007-03-11 kickino StatusNone => Wait reply
        Assigned toNone => kickino

    Back to the top

    Powered by Savane 3.5