No content changes, just split by sect1 and proper linking and adding the new
files along with the above mentioned comments, diff attached
OK.
Goba
On Thursday 15 January 2004 13:12, Gabor Hojtsy wrote:
> > > > splitting huge files makes life for translation teams easier.
> > > > Therefore I am always +1 for splitting.
> > > >
> > > > The functions source xml-files are read for review :
> > > > http://www.holliwell.de/security/security.tar.bz2
> > > splitting huge files makes life for translation teams easier. Therefore I
> > > am always +1 for splitting.
> > >
> > > The functions source xml-files are read for review :
> > > http://www.holliwell.de/security/security.tar.bz2
> > > along with the compiled security chapter:
> > > http://www
On Wednesday 14 January 2004 17:19, Gabor Hojtsy wrote:
> > splitting huge files makes life for translation teams easier. Therefore I
> > am always +1 for splitting.
> >
> > The functions source xml-files are read for review :
> > http://www.holliwell.de/security/security.tar.bz2
> > along with the
> > splitting huge files makes life for translation teams easier. Therefore
> I am
> > always +1 for splitting.
> >
> > The functions source xml-files are read for review :
> > http://www.holliwell.de/security/security.tar.bz2
> > along with the compiled security chapter:
> http://www.holliwell.de
> splitting huge files makes life for translation teams easier. Therefore I am
> always +1 for splitting.
>
> The functions source xml-files are read for review :
> http://www.holliwell.de/security/security.tar.bz2
> along with the compiled security chapter: http://www.holliwell.de/security/
As i
Hi,
splitting huge files makes life for translation teams easier. Therefore I am
always +1 for splitting.
The functions source xml-files are read for review :
http://www.holliwell.de/security/security.tar.bz2
along with the compiled security chapter: http://www.holliwell.de/security/
Friedhelm
