[tex-hyphen] web interface for SVN

[Mojca Miklavec]

On Thu, Jun 12, 2008 at 11:58 PM, Karl Berry wrote:
>    OK. I will let you do that then, but if you need, I can generate
>    those files.
>
> Is it really so easy for you to do so?  There are all kinds of weird
> aliases in those files which (I suppose) we do not want to remove.  I
> can't see how you could autogenerate them from the info you have.

I have generated & commited the separate .dat files now (and the
script generates .tlpscr files which I did not commit; you can run
generate-pattern-loaders.rb yourself at the moment), but it's still a
tiny bit incomplete in cases where more than one language needs to be
joined together. Aliases are all there.

I can fix those cases with joined languages to simplify some dummy
work that you would need to do manually.

One question regarding tlpsrc: old patterns need to be kept on TeX
Live. If one chooses to install hyphen-slovenian, then the old file
doesn't need to be installed. But under what condition would the old
file be installed then? Is there a need for something like
hyphen-legacy.tlpsrc package where all the old files would be listed?

Should files like slhyph.tex be already moved to obsolete now,
together with a readme note? (Not with the intention to remove them in
future, but with intention to warn people that they should better
start using new files.)

Old German, French, Latin, ... patterns definitely need to stay where
they are, we're still using them. For greek we need the version 5 of
patterns. I left them in repository for now (needed for testing). I
have no idea whether we should also keep all the needed old patterns
(such as German) in our repository - that's definitely up to you.

>    If you have any name & structure suggestion, let me know -
>
> You still also want TEXMF/source/generic/hyph-utf-8 for the scripts and
> such?  Unless you don't want to bother distributing them.  I'd prefer to
> have them, though.

Added (well, moved to another location).

> Anyway, please create a draft and I'll comment.  It's easier to refine
> a real instantation than figure it all out in a void.

Done. But maybe I'll call the top level TDS instead of hyph-utf8.

>    Actually, I also need to add a note to all the other converted files.
>    What should I put on top of those files? We need to tell:
>    - who & when converted the file
>
> I'm not sure the "who" is important, but you could just include a `date`
> string for the "when" in the autogenerated header.  I agree that would
> be nice.
>
>    - a note saying: "please do not add any TeX macros to this file"
>
> The note should say "This file was automatically generated, do not edit."
> TeX macros or anything else :).

But the patterns themselves were not auto-generated. They had to be
checked for different conventions, some have been joined from more
than a single file, and some parts had to be removed.

> Yep, contact info is always good, but I wouldn't put an email in the
> files; instead I'd put a url, namely http://tug.org/tex-hyphen.

Done. It points to non-existing web page at the moment, but I suspect
there will be one :)

>  One of
> us can create a simple web page with pointers to the mailing list, svn
> tree, etc.

Mojca

short important-but-not-for-testing TODO list:
- add messages like "Foo hyphenation patterns" to generate-pattern-loaders.rb
- add copyright notes (more like - "change notes") to hyph-xx.tex to
make it clear what we did from which files
- probably some other things as well