> If you are not sure, how you can break the automatic manual build
> and all translations, so don´t introduce new folders.
I didn't. We are just thinking about new folders.
Mark
From: "Mark Kronsbein" <[EMAIL PROTECTED]>
> > manual.xml is needed. I say do not hurry with this, as it makes
> > all translations translated install parts be replaced with
> > English, as long as they do not start translation of files.
>
> Yes. And the translation of the files should not start
> manual.xml is needed. I say do not hurry with this, as it makes
> all translations translated install parts be replaced with
> English, as long as they do not start translation of files.
Yes. And the translation of the files should not start until we/I are
finished with splitting and know, how
> this is not entirely true, the entities used in install.xml
> are still defined in entities/chapters.ent which is auto
> generated by configure, using translated files where possible
> with a fallback to english originals
Oh. So this "problem" Gabor described in his last mail is not really a
"
> OK. Please do not only ACK my folder ideas, but please also
> give your opinion. For example whether it would be better
> to put condigure things into install/configure or configure/.
Installation -> install/ Configure Options -> install/configure
php.ini Stuff/configuration directives -> inst
philip Mon Jan 14 21:51:07 2002 EDT
Modified files:
/phpdoc TODO
Log:
TODO: Document all BC Breaks and Deprecations, at a single location.
Index: phpdoc/TODO
diff -u phpdoc/TODO:1.18 phpdoc/TODO:1.19
--- phpdoc/TODO:1.18Mon Jan 14 15:21:14 2002
+++
> I have now made a test myself with my old system. If you have a
> correct DocBook installation, you should see no errors.
I'm hoping someone can help me see what's wrong so I can fix. I've tried,
and failed.
>From the errors, any ideas? I'm desperate here :)
Regards,
Philip Olson
gerzson Mon Jan 14 18:50:04 2002 EDT
Modified files:
/phpdoc/hu/functionsbzip2.xml
Log:
present the EN-revision comment
Index: phpdoc/hu/functions/bzip2.xml
diff -u phpdoc/hu/functions/bzip2.xml:1.1 phpdoc/hu/functions/bzip2.xml:1.2
--- phpdoc/hu/funct
jkj Mon Jan 14 17:12:59 2002 EDT
Modified files:
/phpdoc/dsssl html-common.dsl print.dsl.in
Log:
Added support for
Index: phpdoc/dsssl/html-common.dsl
diff -u phpdoc/dsssl/html-common.dsl:1.1 phpdoc/dsssl/html-common.dsl:1.2
--- phpdoc/dsssl/html-
> We use since 1997 The Chicago Manual of Style and now EOD.
Not sure why I brought it up actually.
Philip
Egon Schmid wrote:
> Oh, haven´t known that. Can it do the following in English:
>
> See also: func1 and func2.
> See also: func1, func2, and func3.
>
> and for German or Hungarian:
>
> Siehe auch: func1 und func2.
> Siehe auch: func1, func2 und func3.
>
> Look at the commas.
Yes, exactly. (
From: "Philip Olson" <[EMAIL PROTECTED]>
> > See also: func1 and func2.
> > See also: func1, func2, and func3.
> >
> > and for German or Hungarian:
> >
> > Siehe auch: func1 und func2.
> > Siehe auch: func1, func2 und func3.
>
> Btw, it's okay english (perfectly acceptable) to not put a comma
bef
> See also: func1 and func2.
> See also: func1, func2, and func3.
>
> and for German or Hungarian:
>
> Siehe auch: func1 und func2.
> Siehe auch: func1, func2 und func3.
Btw, it's okay english (perfectly acceptable) to not put a comma before
the and here, so:
See also: func1, func2 and func3
Gabor Hojtsy wrote:
> Two reasons, speed and customization level. Not all DSSSL customizations
> are ported to XSL customizations. This is in the TODO in BUILD SYSTEM
If you tell my which, I can port them.
--
-
Jirka Kosek
From: "Jirka Kosek" <[EMAIL PROTECTED]>
Egon Schmid wrote:
> > I don´t have something against a rendering a "see also" block.
But
> > rendering the content with a list would be a nightmare. We had a
> > discussion at which place should be comma in this list. This
depends
> > on the language and
Egon Schmid wrote:
> I don´t have something against a rendering a "see also" block. But
> rendering the content with a list would be a nightmare. We had a
> discussion at which place should be comma in this list. This depends
> on the language and I can guess it will be look very funny in
> Arabi
From: "Jirka Kosek" <[EMAIL PROTECTED]>
> I finished modification of DSSSL stylesheets. They are 100%
backward
> compatible -- rendering is changed only on notes with
role="seealso". If
> you decide not to use it, you can always delete this rule in
future.
> Egon, can I commit it before I forget
gobaMon Jan 14 15:21:14 2002 EDT
Modified files:
/phpdoc TODO
Log:
Added more from my dreams, with **needs discussion** marks
Index: phpdoc/TODO
diff -u phpdoc/TODO:1.17 phpdoc/TODO:1.18
--- phpdoc/TODO:1.17Mon Jan 14 15:08:01 2002
+++ phpdoc/TOD
> I don´t have something against a rendering a "see also" block.
> But rendering the content with a list would be a nightmare. We had a
> discussion at which place should be comma in this list. This depends
> on the language and I can guess it will be look very funny in
> Arabic.
>
> > I see no pr
From: "Jirka Kosek" <[EMAIL PROTECTED]>
Egon Schmid wrote:
> > Jirka, please don´t make changes for the rendering of the "see
also"
> > notes until there is a solution for the incomplete PDF manuals.
IMHO
> > it is an overkill.
> You mean: overkill = too much markup?
Yes.
> In general you are
> > HTML Help will definetly render the see also parts with different
> > style. Now I have implemented some auto detection with some
> > ugly text processing, searching for "see also:" commas and "and"
> > words, and detected the see also parts this way for the HTML Help
> > generation. This is n
hholzgraMon Jan 14 15:08:01 2002 EDT
Modified files:
/phpdoc TODO
Log:
Index: phpdoc/TODO
diff -u phpdoc/TODO:1.16 phpdoc/TODO:1.17
--- phpdoc/TODO:1.16Mon Jan 14 14:58:07 2002
+++ phpdoc/TODO Mon Jan 14 15:08:01 2002
@@ -32,6 +32,7 @@
Egon Schmid wrote:
> Jirka, please don´t make changes for the rendering of the "see also"
> notes until there is a solution for the incomplete PDF manuals.
how are these two topics related? have i missed something?
> IMHO it is an overkill.
> It is much better to write the "see also" notes
Gabor Hojtsy wrote:
>
> > In general you are right, but marking some block as "seealso" can be
> > very usefull when rendering and converting to other formars (e.g. HTML
> > Help).
>
> HTML Help will definetly render the see also parts with different
> style. Now I have implemented some auto det
gobaMon Jan 14 14:58:07 2002 EDT
Modified files:
/phpdoc TODO
Log:
Adding some parts from my whislist, the ones we already agreed on,
that these are desireable
Index: phpdoc/TODO
diff -u phpdoc/TODO:1.15 phpdoc/TODO:1.16
--- phpdoc/TODO:1.15Sun
Hi,
I usually find usefull code in the function reference pages of www.php.net
If I want to include those code in my aplication, should I be aware of some
license?
Are they GPL or freeware?
Should I include a "Credits" page in my Aplication/Documentation?
Thanks
Oliver
--
Oliver Schulze L.
[EMA
> > this is not entirely true, the entities used in install.xml
> > are still defined in entities/chapters.ent which is auto
> > generated by configure, using translated files where possible
> > with a fallback to english originals
> >
> > the only thing that might lead to outdated material or b
> In general you are right, but marking some block as "seealso" can be
> very usefull when rendering and converting to other formars (e.g. HTML
> Help).
HTML Help will definetly render the see also parts with different
style. Now I have implemented some auto detection with some
ugly text processi
Egon Schmid wrote:
> Jirka, please don´t make changes for the rendering of the "see also"
> notes until there is a solution for the incomplete PDF manuals. IMHO
> it is an overkill.
You mean: overkill = too much markup?
In general you are right, but marking some block as "seealso" can be
very u
> > Now, we need to discuss where they should go. I would be fine
> > with phpdoc/install for install.anything.xml files, and
> > phpdoc/install/configure or phpdoc/configure for
> > install.configure.anything.xml files.
>
> phpdoc/en/install and phpdoc/en/configure?
OK for me. IMHO both Instal
gobaMon Jan 14 14:47:02 2002 EDT
Modified files:
/phpdoc/hu language-defs.ent
Log:
Add Installatoin entity, though it is not used, but it will be used.
Index: phpdoc/hu/language-defs.ent
diff -u phpdoc/hu/language-defs.ent:1.9 phpdoc/hu/language-defs.en
gobaMon Jan 14 14:43:25 2002 EDT
Modified files:
/phpdoc/en language-defs.ent
Log:
Adding language def for install.xml. All languages using the english
install section *SHOULD* add this entity to language-defs.ent to make
their build work.
Index: ph
> this is not entirely true, the entities used in install.xml
> are still defined in entities/chapters.ent which is auto
> generated by configure, using translated files where possible
> with a fallback to english originals
>
> the only thing that might lead to outdated material or breaks
> woul
gobaMon Jan 14 14:40:02 2002 EDT
Added files:
/phpdoc/en/chapters install.general.xml
Modified files:
/phpdoc/en/chapters install.xml
Log:
Make Installation part translation friendly, now install.xml should
not be translated or copie
> > As nobody else complained,
>
> didn't i?
Yes, sorry :) Jirkas, idea solves the list problem,
as I can see, while also allows us to use simple text if a list
is not appropriate. What do you think abut this?
Goba
> > IMHO is on semantic level very close to seealso. Using role
> > is standard DocBook way to make it different from standard note.
>
> Jirka, please don´t make changes for the rendering of the "see also"
> notes until there is a solution for the incomplete PDF manuals. IMHO
> it is an overkill.
Gabor Hojtsy wrote:
> Using entities in install.xml is completely against our
> automatic translation handling system (chapters ent
> generation). If one deletes an entity or forget to add
> one, that particular part won't be addded to the doc.
> This is wht the automatic translation handling sys
Egon Schmid wrote:
> eschmid Sat Jan 12 15:09:32 2002 EDT
>
> Modified files:
> /phpdoc funclist.txt funcsummary.txt
> Log:
> Update of funclist.txt and funcsummary.txt
do we realy need these auto generated files in CVS,
or are they just left over from
Jim Winstead wrote:
> it is broken because the system builds the manual outside of the phpdoc
> tree. that means when $(srcdir) isn't properly used, the build breaks.
>
> this is easy to test and fix on any (unix) system -- just make an empty
> directory, and run phpdoc's configure from there (u
Gabor Hojtsy wrote:
> Now, we need to discuss where they should go. I would be fine
> with phpdoc/install for install.anything.xml files, and
> phpdoc/install/configure or phpdoc/configure for
> install.configure.anything.xml files.
phpdoc/en/install and phpdoc/en/configure?
--
Hartmut Holzg
Philip Olson wrote:
>>BTW which problems do you have building the HTM manual locally?
>>
>
> In doing this:
>
> make clean; autoconf; ./configure; make html > junk 2>&1
>
> The first few lines of 'junk' is as follows. I used to have this
> problem with 'make test' until jim's patch 1.99
Egon Schmid wrote:
> From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>
>
>>>eschmid Sat Jan 12 15:09:32 2002 EDT
>>>
>>> Modified files:
>>>/phpdoc funclist.txt funcsummary.txt
>>> Log:
>>> Update of funclist.txt and funcsummary.txt
>>>
>>do we realy need these auto generated files in CVS,
>
Gabor Hojtsy wrote:
> As nobody else complained,
didn't i?
--
Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
From: "Jirka Kosek" <[EMAIL PROTECTED]>
> Gabor Hojtsy wrote:
>
> > > What is the exact syntax, will we still be defining commas and
'and'
> > > within the blocks?
> >
> > Yes. It seems that using lists is much more complex for the
rendering,
> > as it involves adding commas and and words only wh
>
>
> print
> echo
>
>
>
> Once again, you must wrap it inside para:
>
>
>
> print, and
> the notes on the CGI
> security page
>
>
>
> IMHO is on semantic level very close to seealso. Using role is
> standard DocBook way to make it different from standard note.
IMHO we can go
> > > > > Modules like iisfunc are moved to pear/PECL.
> > > > > Documents for them should be moved to pear.
> > > > >
> > > > > Or am I wrong?
> > > >
> > > > Yes.
> > >
> > > It would be nice if the documentation is kept in one place so
> > people don't
> > > have to remember where the function
> > Now, we need to discuss where they should go. I would be fine
> > with phpdoc/install for install.anything.xml files, and
> > phpdoc/install/configure or phpdoc/configure for
> > install.configure.anything.xml files.
>
> Yes, ack.
>
> > phpdoc/configure/databases.xml
> ...
> > phpdoc/config
Gabor Hojtsy wrote:
> > What is the exact syntax, will we still be defining commas and 'and'
> > within the blocks?
>
> Yes. It seems that using lists is much more complex for the rendering,
> as it involves adding commas and and words only where needed
> programatically.
>
>
> print, and
>
From: "Philip Olson" <[EMAIL PROTECTED]>
> > BTW which problems do you have building the HTM manual locally?
>
> In doing this:
>
> make clean; autoconf; ./configure; make html > junk 2>&1
>
> The first few lines of 'junk' is as follows. I used to have this
> problem with 'make test' until jim
> > > If I understand it correctly, see-also block is very simillar to
> > > admonitions (note, warning, ...). So what about putting see-also
inside
> > > note
> > >
> > >
> > > ...
> > >
> > >
> > > Stylesheet can render it differently than note w/o role="seealso".
> >
> > As nobody else compla
> > If I understand it correctly, see-also block is very simillar to
> > admonitions (note, warning, ...). So what about putting see-also inside
> > note
> >
> >
> > ...
> >
> >
> > Stylesheet can render it differently than note w/o role="seealso".
>
> As nobody else complained, I think we ca
> If I understand it correctly, see-also block is very simillar to
> admonitions (note, warning, ...). So what about putting see-also inside
> note
>
>
> ...
>
>
> Stylesheet can render it differently than note w/o role="seealso".
As nobody else complained, I think we can go on with this styl
> which version of dsssl stylesheets do you use?
docbook-dsssl 1.74b-1 latest debian sid package.
> BTW which problems do you have building the HTM manual locally?
In doing this:
make clean; autoconf; ./configure; make html > junk 2>&1
The first few lines of 'junk' is as follows. I used to have this
problem with 'make test' until jim's patch 1.99 on Makefile.ini
titled "don't make te
From: "Edin Kadribasic" <[EMAIL PROTECTED]>
> > > > > Modules like iisfunc are moved to pear/PECL.
> > > > > Documents for them should be moved to pear.
> > > > >
> > > > > Or am I wrong?
> > > >
> > > > Yes.
> > >
> > > It would be nice if the documentation is kept in one place so
> > people don
> > > > Modules like iisfunc are moved to pear/PECL.
> > > > Documents for them should be moved to pear.
> > > >
> > > > Or am I wrong?
> > >
> > > Yes.
> >
> > It would be nice if the documentation is kept in one place so
> people don't
> > have to remember where the function came from.
>
> Do yo
From: "Edin Kadribasic" <[EMAIL PROTECTED]>
> > > Modules like iisfunc are moved to pear/PECL.
> > > Documents for them should be moved to pear.
> > >
> > > Or am I wrong?
> >
> > Yes.
>
> It would be nice if the documentation is kept in one place so
people don't
> have to remember where the func
> > Modules like iisfunc are moved to pear/PECL.
> > Documents for them should be moved to pear.
> >
> > Or am I wrong?
>
> Yes.
It would be nice if the documentation is kept in one place so people don't
have to remember where the function came from.
Edin
From: "Yasuo Ohgaki" <[EMAIL PROTECTED]>
> Hi all,
>
> Modules like iisfunc are moved to pear/PECL.
> Documents for them should be moved to pear.
>
> Or am I wrong?
Yes.
-Egon
From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>
> > eschmid Sat Jan 12 15:09:32 2002 EDT
> >
> > Modified files:
> > /phpdoc funclist.txt funcsummary.txt
> > Log:
> > Update of funclist.txt and funcsummary.txt
>
> do we realy need these auto generated files in CVS,
These files are not a
Hi all,
Modules like iisfunc are moved to pear/PECL.
Documents for them should be moved to pear.
Or am I wrong?
--
Yasuo Ohgaki
gerzson Mon Jan 14 10:55:41 2002 EDT
Modified files:
/phpdoc/hu translation.xml
Log:
new nick and remove bzip2.xml from work-in-progress
Index: phpdoc/hu/translation.xml
diff -u phpdoc/hu/translation.xml:1.4 phpdoc/hu/translation.xml:1.5
--- phpdoc/hu/translat
gerzson Mon Jan 14 10:54:52 2002 EDT
Added files:
/phpdoc/hu/functionsbzip2.xml
Log:
bzip2 translation ended and here comes
Index: phpdoc/hu/functions/bzip2.xml
+++ phpdoc/hu/functions/bzip2.xml
Bzip2 tömörítési függvények
Bzip2
zimtMon Jan 14 10:33:40 2002 EDT
Modified files:
/phpdoc/de/functionsoutcontrol.xml
Log:
added space between "void" and "ob_start"...
Index: phpdoc/de/functions/outcontrol.xml
diff -u phpdoc/de/functions/outcontrol.xml:1.7 phpdoc/de/functions/outcon
Shlomi Loubaton wrote:
> Gabor/anyone, I still need some DSSSL expert to help me with the
> "dir=rtl/align=right" problem ... so if you know someone like that - just
> send me his email.
You can send your question to [EMAIL PROTECTED] -- this
is specialized DocBook processing list.
You can als
Nir Dagan wrote:
> Hello,
>
> Summary: One may produce Hebrew pages with output in either ISO-8859-8 or
> ISO-8859-8-i, but SHOULD serve them as ISO-8859-8-i over the web.
>
> Strictly speaking ISO-8859-8 and ISO-8859-8-i
> are the same encoding. Namely, they assign identical bytes to the same
> c
Hello,
Summary: One may produce Hebrew pages with output in either ISO-8859-8 or
ISO-8859-8-i, but SHOULD serve them as ISO-8859-8-i over the web.
Strictly speaking ISO-8859-8 and ISO-8859-8-i
are the same encoding. Namely, they assign identical bytes to the same
characters.
Howver due to histo
hholzgraMon Jan 14 07:41:02 2002 EDT
Modified files:
/phpdoc configure.in
Log:
removed unnecessary "./" breaking builds with absolute path to srcdir
added some debug output (configure line and file versions) for build.log
Index: phpdoc/configur
Hi Gabor!
> Now, we need to discuss where they should go. I would be fine
> with phpdoc/install for install.anything.xml files, and
> phpdoc/install/configure or phpdoc/configure for
> install.configure.anything.xml files.
Yes, ack.
> phpdoc/configure/databases.xml
...
> phpdoc/configure/xml.x
> > OK, for the SP encoding (we need this for HTML generation),
> > these seems to be good:
> >
> > is8859-n or iso-8859-n
> > n can be any single digit other than 0. Each character in the
> > repertoire of ISO 8859-n is represented by a single byte.
> >
> > Now the question to Shlomi is
gobaMon Jan 14 05:42:59 2002 EDT
Modified files:
/phpdoc configure.in
Log:
Added SP and HTML HELP encodings, using iso-8859-8. Palm title need
to be added later (when it turns out how the manual is called in Hebrew,
and if there is any Palm support for
> OK, for the SP encoding (we need this for HTML generation),
> these seems to be good:
>
> is8859-n or iso-8859-n
> n can be any single digit other than 0. Each character in the
> repertoire of ISO 8859-n is represented by a single byte.
>
> Now the question to Shlomi is that what -i
> Well, supporting Hebrew, do not seem to be that easy :(
> It seems that there is no Windows HTML Help setting for
> this. I also searched the jade distribution, and found
> only one mention of Hebrew, and it was in a comment... :((
OK, for the SP encoding (we need this for HTML generation),
the
Well, supporting Hebrew, do not seem to be that easy :(
It seems that there is no Windows HTML Help setting for
this. I also searched the jade distribution, and found
only one mention of Hebrew, and it was in a comment... :((
Goba
> ok, but for now, i'm sure that HTML formatting is possible.
> I preformed a little test .. I downloaded the 'en' CVS manual, translated
> preface.xml and some .ent files , then I rebuilt the manual with the 'many
> html' option (i did that localy ofcrz). Then i had to edit the preface
html
> fil
gobaMon Jan 14 05:22:03 2002 EDT
Modified files:
/phpdoc configure.in
Log:
Default enconding for "he". HTML Help, SP, and Palm encondings and
titles also need to be added later...
Index: phpdoc/configure.in
diff -u phpdoc/configure.in:1.112 phpdoc/
Jirka Kosek wrote:
> In lang attribute you should use just language code not full name. It is
> "he" for Hebrew and "en" for English.
>
> But you may come in serious problems when formatting your documents --
> many current tools didn't have suport for rtl text flow.
>
> Jirka
ok, but for now, i
> Another thing: where is general installation
> steps in the breaked up install parts? Its nowhere!!
> Are there other parts left out? Can anybody please check?
OK, I was a bit confused here with the structure. I have
just realized that multi-level includes were used (manual.xml
used chapters.in
philip Mon Jan 14 04:45:56 2002 EDT
Modified files:
/phpdoc/en/functionsmath.xml
Log:
pi: Document precicion directive's affect, as well as the M_PI constant.
And, some other minor changes.
Index: phpdoc/en/functions/math.xml
diff -u phpdoc/en/fun
philip Mon Jan 14 04:42:30 2002 EDT
Modified files:
/phpdoc/en/chapters config.xml
Log:
precision: Document the precision directive.
Index: phpdoc/en/chapters/config.xml
diff -u phpdoc/en/chapters/config.xml:1.32 phpdoc/en/chapters/config.xml:1.33
--- phpdo
> /phpdoc/ja/chapters install.apache.xml install.caudium.xml
>install.commandline.xml
>install.configure.databases.xml
>install.configure.graphics.xml
>install.configure.misc.xml
>
gobaMon Jan 14 04:34:50 2002 EDT
Added files:
/phpdoc/en/chapters DO_NOT_TRANSLATE
Log:
Adding warning file, to try to stop people doing what they really do not want to do
fujimotoMon Jan 14 04:33:36 2002 EDT
Modified files:
/phpdoc/ja/language control-structures.xml functions.xml
Log:
translation updated.
Index: phpdoc/ja/language/control-structures.xml
diff -u phpdoc/ja/language/control-structures.xml:1.25
phpdoc/ja
Shlomi Loubaton wrote:
> There are some some issues left to solve with the docbook stylesheets.
> I'll need your help for that. One of the problems is adding a support for
> right to left paragraphs:
>
> This text is right to left, this is left to
> right.
>
In lang attribute you should use ju
Hi !
Please help me to create a 'he' directory for the hebrew translation.
I already have a CVS account.
We'll be using the iso-8859-8-i encoding.
There are some some issues left to solve with the docbook stylesheets.
I'll need your help for that. One of the problems is adding a support for
rig
85 matches
Mail list logo
