Re: [PHP-DOC] Finnish translation..(was: Re: [PHP-DOC] Revisioncheck, now working)
On Sun, 2 Sep 2001, Jani Taskinen wrote: On Sun, 2 Sep 2001, Jouni Ahto wrote: because he finds the exactly same things extremely useful. And if I would start a Finnish translation, I too would find them useful, so I side with Would you? :) Someone asked for CVS account for translating the manual to finnish some time ago. He didn't get the account I think.. A pity. Maybe he sent an example of his work and nobody in the group did understand a word about it, which in itself would have been a good reason to give that account... I could help a little on translating but I don't wanna do that all the time. :) Same thing. Not enough time. -- Jouni
[PHP-DOC] cvs: phpdoc /hu/functions image.xml
kgergelyMon Sep 3 08:35:02 2001 EDT Modified files: /phpdoc/hu/functionsimage.xml Log: English revision added Index: phpdoc/hu/functions/image.xml diff -u phpdoc/hu/functions/image.xml:1.10 phpdoc/hu/functions/image.xml:1.11 --- phpdoc/hu/functions/image.xml:1.10 Sat Sep 1 19:49:36 2001 +++ phpdoc/hu/functions/image.xml Mon Sep 3 08:35:02 2001 @@ -1,5 +1,5 @@ ?xml encoding=iso-8859-2? -!-- EN-Revision: n/a Maintainer: kgergely Status: en/hu mixed -- +!-- EN-Revision: 1.33 Maintainer: kgergely Status: en/hu mixed -- reference id=ref.image titleKépmanipuláló függvények/title
[PHP-DOC] cvs: phpdoc / manual.xml.in /cs language-defs.ent /de language-defs.ent /en language-defs.ent /es language-defs.ent /fr language-defs.ent /hk language-defs.ent /hu language-defs.ent /it language-defs.ent /ja language-defs.ent /kr language-defs.ent /nl language-defs.ent /pt_BR language-defs.ent /tr language-defs.ent
ssb Mon Sep 3 08:34:59 2001 EDT Modified files: /phpdoc manual.xml.in /phpdoc/cs language-defs.ent /phpdoc/de language-defs.ent /phpdoc/en language-defs.ent /phpdoc/es language-defs.ent /phpdoc/fr language-defs.ent /phpdoc/hk language-defs.ent /phpdoc/hu language-defs.ent /phpdoc/it language-defs.ent /phpdoc/ja language-defs.ent /phpdoc/kr language-defs.ent /phpdoc/nl language-defs.ent /phpdoc/pt_BR language-defs.ent /phpdoc/tr language-defs.ent Log: * added titleabbrev tags for PEAR and FAQ to clean up left sidebar in online manual Index: phpdoc/manual.xml.in diff -u phpdoc/manual.xml.in:1.79 phpdoc/manual.xml.in:1.80 --- phpdoc/manual.xml.in:1.79 Sun Aug 12 10:26:36 2001 +++ phpdoc/manual.xml.inMon Sep 3 08:34:52 2001 @@ -165,6 +165,7 @@ part id=pear titlePEAR;/title + titleabbrevPEAR/titleabbrev pear.about; pear.standards; pear.pear; @@ -175,6 +176,7 @@ part id=faq titleFAQ;/title + titleabbrevFAQabbrev;/titleabbrev faq.general; faq.mailinglist; faq.obtaining; Index: phpdoc/cs/language-defs.ent diff -u phpdoc/cs/language-defs.ent:1.4 phpdoc/cs/language-defs.ent:1.5 --- phpdoc/cs/language-defs.ent:1.4 Wed Jul 11 18:08:21 2001 +++ phpdoc/cs/language-defs.ent Mon Sep 3 08:34:52 2001 @@ -8,3 +8,4 @@ !ENTITY AppendixesDodatky !ENTITY PEAR PEAR: the PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/de/language-defs.ent diff -u phpdoc/de/language-defs.ent:1.4 phpdoc/de/language-defs.ent:1.5 --- phpdoc/de/language-defs.ent:1.4 Wed Jul 11 18:08:21 2001 +++ phpdoc/de/language-defs.ent Mon Sep 3 08:34:53 2001 @@ -7,3 +7,4 @@ !ENTITY AppendixesAnhang !ENTITY PEAR PEAR: the PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/en/language-defs.ent diff -u phpdoc/en/language-defs.ent:1.7 phpdoc/en/language-defs.ent:1.8 --- phpdoc/en/language-defs.ent:1.7 Sun Aug 19 07:55:42 2001 +++ phpdoc/en/language-defs.ent Mon Sep 3 08:34:53 2001 @@ -1,4 +1,4 @@ -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- !ENTITY PHPManual PHP Manual !ENTITY Date Date: @@ -9,3 +9,4 @@ !ENTITY AppendixesAppendixes !ENTITY PEAR PEAR: the PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/es/language-defs.ent diff -u phpdoc/es/language-defs.ent:1.3 phpdoc/es/language-defs.ent:1.4 --- phpdoc/es/language-defs.ent:1.3 Wed Jul 11 18:08:21 2001 +++ phpdoc/es/language-defs.ent Mon Sep 3 08:34:53 2001 @@ -7,3 +7,4 @@ !ENTITY AppendixesApeacute;ndices !ENTITY PEAR PEAR: the PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/fr/language-defs.ent diff -u phpdoc/fr/language-defs.ent:1.3 phpdoc/fr/language-defs.ent:1.4 --- phpdoc/fr/language-defs.ent:1.3 Wed Jul 11 18:08:21 2001 +++ phpdoc/fr/language-defs.ent Mon Sep 3 08:34:54 2001 @@ -7,3 +7,4 @@ !ENTITY AppendixesAppendices !ENTITY PEAR PEAR: the PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/hk/language-defs.ent diff -u phpdoc/hk/language-defs.ent:1.2 phpdoc/hk/language-defs.ent:1.3 --- phpdoc/hk/language-defs.ent:1.2 Wed Jul 11 18:08:22 2001 +++ phpdoc/hk/language-defs.ent Mon Sep 3 08:34:54 2001 @@ -7,3 +7,4 @@ !ENTITY Appendixesªþ¥ó !ENTITY PEAR PEAR: PHP Extension and Application Repository !ENTITY FAQ FAQ: Frequently Asked Questions +!ENTITY FAQabbrev FAQ Index: phpdoc/hu/language-defs.ent diff -u phpdoc/hu/language-defs.ent:1.6 phpdoc/hu/language-defs.ent:1.7 --- phpdoc/hu/language-defs.ent:1.6 Thu Aug 30 11:37:44 2001 +++ phpdoc/hu/language-defs.ent Mon Sep 3 08:34:55 2001 @@ -9,6 +9,7 @@ !ENTITY Appendixes Függelékek !ENTITY PEAR PEAR: PHP Extension and Application Repository !ENTITY FAQGYIK: Gyakran Ismételt Kérdések +!ENTITY FAQabbrev GYIK !ENTITY url.hu.weblaborhttp://weblabor.hu/; !ENTITY email.hu.php [EMAIL PROTECTED] Index: phpdoc/it/language-defs.ent diff -u phpdoc/it/language-defs.ent:1.5 phpdoc/it/language-defs.ent:1.6 --- phpdoc/it/language-defs.ent:1.5 Mon Aug 6 13:59:03 2001 +++ phpdoc/it/language-defs.ent Mon Sep 3 08:34:55 2001 @@ -7,3 +7,4 @@ !ENTITY AppendixesAppendici !ENTITY PEAR PEAR: Archivio delle estensioni ed applicazioni in PHP !ENTITY FAQ
[PHP-DOC] cvs: phpdoc /it Translators
peruginiMon Sep 3 08:53:18 2001 EDT Modified files: /phpdoc/it Translators Log: Typo fixed. Index: phpdoc/it/Translators diff -u phpdoc/it/Translators:1.48 phpdoc/it/Translators:1.49 --- phpdoc/it/Translators:1.48 Tue Aug 28 16:19:47 2001 +++ phpdoc/it/Translators Mon Sep 3 08:53:18 2001 @@ -28,6 +28,7 @@ version from which the italian one is going to be made or has been made. If no version is given in the last column, we will add it at a later date. + T = translater A = assigned
Re: [PHP-DOC] Revision check, now working
There is no problem though when there is an english typo-fix. The report will show that the translation is a bit behind, but then you can simply 'update' it. (by only modifying the infoline). This doesn't break anything. Besides, when a translator who finds that a translation that corresponds to english version 1.65 and the translation is EN:Revision 1.63, will find *very* quickly if there were some changes that should be translated, or if they were just typo/WS fixes. This isn't actually a big issue, more like a cosmetical one, the revision numbers sometimes might not being totally in-sync with each other. And the same thing is for Translators. The same information is stored in revision comments and they need to be updated the same time as the Translators file, they are just stored in the files themselfs. Goba
[PHP-DOC] Fw: Translating docs
Forwarded to [EMAIL PROTECTED] Goba [one [EMAIL PROTECTED]] - Original Message - From: Petr Klika [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 03, 2001 9:37 AM Subject: Translating docs Hi, sorry if I send this email to wrong place, I didn't find anything better. I would like to translate some pages of the Czech manual. How can I do it? Petr
Re: [PHP-DOC] Revision check, now working
BETTER: The generated revcheck.html is not a file to store history about. So there is no need to put the generated revcheck.html files for the languages in CVS. I don´t understand. CVS is a system to store the files modification history. It is a used to track changes, and store the files history. The revcheck.html generated by the revcheck.php script is not a file we need to store history about. We are only interested in the actual state. So there is no need to store revcheck.html in CVS. It can be hosted and updated on an external server as /~rasmus/status.php is. To make the story short. German translators don´t need a revision number or a revision comment. Then why do you add revision numbers to the de/Translators file??? Why do you spend (and spent) time with useless things yourself? Some commit messages from you I have found: |eschmid Sat Apr 14 02:37:27 2001 EDT | | Modified files: |/phpdoc/de Translators |/phpdoc/de/functions filesystem.xml | Log: | Update by Thomas Schöfbeck. Still not sure to which English version. Another one, when you are adding that revision: |eschmid Tue Apr 24 00:36:13 2001 EDT | | Modified files: |/phpdoc/de Translators | Log: | Changed version number, | |Index: phpdoc/de/Translators |diff -u phpdoc/de/Translators:1.153 phpdoc/de/Translators:1.154 |--- phpdoc/de/Translators:1.153 Mon Apr 16 13:26:33 2001 |+++ phpdoc/de/Translators Tue Apr 24 00:36:12 2001 |@@ -75,7 +75,7 @@ | exec.xmlWolfgang Drews in Arbeit | fdf.xml | filepro.xml Martin Jansen fertig |-filesystem.xml Wolfgang Drews + Thomas fertig (not sure) |+filesystem.xml Wolfgang Drews + Thomas fertig (bis V. 1.61) Then why it was so important in April to know what revision the file corresponds to in the english tree??? And why are the other (you say useless) revision numbers are stored in de/Translators? I say why: because it eases the updates. I can't find that letter, when you adviced the de translators to write down the revision numbers in the Translators file, but there were one letter from you about this subject... We need the diffs up to that date, when the original translator or maintainer leaved the project. It is impossible to make a script which tells a new translator he have to add, delete or to modify. I hope you understand this. Again, if you don't know the revision, it is useless, but the time, when you find the revision, it helps much to do exact diffs instead of figure out all the time, what was the original english xml file. It can happen, that we get a bug report about a misspelled word and if someone correct this, your revision system would fail. The others reflected to this sentence. It just can't break the system. If you edit the German file, the revision is not changes, if you edit the English file, the script will show that your translation is not up to date. This is also a case if you work from the Translators file or work with dates. If you use Revision comments, they help you in this case, the exact diff will show you, that it was a typo fix, and you can ++ the Revision nunmber in the comment. Goba
[PHP-DOC] cvs: phpdoc /hu/functions image.xml
kgergelyMon Sep 3 11:27:48 2001 EDT Modified files: /phpdoc/hu/functionsimage.xml Log: Cleanup some comments about the english version + found 1 more sentence not translated before. Index: phpdoc/hu/functions/image.xml diff -u phpdoc/hu/functions/image.xml:1.12 phpdoc/hu/functions/image.xml:1.13 --- phpdoc/hu/functions/image.xml:1.12 Mon Sep 3 09:29:59 2001 +++ phpdoc/hu/functions/image.xml Mon Sep 3 11:27:48 2001 @@ -59,7 +59,7 @@ /para para Az opcionális parameterimageinfo/parameter paraméter lehetõvé - teszi néhány plusz információ kinyerését a fileból ['''] + teszi néhány plusz információ kinyerését a fileból. Jelenleg ez a különbözõ acronymJPG/acronym APP jelzéseket asszociatív tömb formájában adja vissza. Néhány program ezeket az APP jelzéseket használja, @@ -114,10 +114,10 @@ Az functionImageArc/function függvény egy ellipszisdarabot rajzol az im-mel azonosított képre parametercx/parameter, parametercy/parameter középponttal (a kép bal felsõ széle a 0, 0). - A parameterw [kis w!]/parameter és a parameterh/parameter + A parameterw/parameter és a parameterh/parameter paraméterek az ellipszis szélességét illetve magasságát határozzák meg. Az ellipszisdarab kezdõ és végpontját fokban a - parameters/parameter és a parametere/parameter[nincs pont] + parameters/parameter és az parametere/parameter adják meg. /para /refsect1 @@ -147,8 +147,8 @@ színnel az parameterid/parameter-vel azonosított képen a betû bal felsõ sarkát az parameterx/parameter,parametery/parameter koordinátához igazítva (a kép bal felsõ széle a 0, 0 pont). - with a color . Ha parameterfont/parameter[kell parameter] - értéke 1, 2, 3, 4 vagy 5, egy beépített font kerül használatra + with a color . Ha parameterfont/parameter + értéke 1, 2, 3, 4 vagy 5, egy beépített betûtípus kerül használatra (nagyobb szám nagyobb fontot jelent). /para para @@ -181,7 +181,7 @@ színnel az parameterid/parameter-vel azonosított képen a betû bal felsõ sarkát az parameterx/parameter,parametery/parameter koordinátához igazítva (a kép bal felsõ széle a 0, 0 pont). - with a color . Ha parameterfont/parameter[kell parameter] + with a color . Ha parameterfont/parameter értéke 1, 2, 3, 4 vagy 5, egy beépített font kerül használatra (nagyobb szám nagyobb fontot jelent). /para @@ -209,8 +209,7 @@ /funcsynopsis para Az functionImageColorAllocate/function egy színkóddal tér vissza, - amelyet a függény a megadotott acronymRGB/acronym komponensekbõl - [] + amely a megadotott acronymRGB/acronym komponensekbõl áll. Az parameterim/parameter paraméter az functionimagecreate/function funkció által visszaadott érték. [Ez még kéne bele... @@ -665,7 +664,7 @@ /para para Az functionImageCreateFromGif/function üres stringgel tér vissza - hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben [???] + hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben A nyomkövetés megkönnyítésére a következõ példa egy hibát jelzõ GIF-et állít elõ. example title @@ -715,7 +714,7 @@ /para para Az functionImageCreateFromJpeg/function üres stringgel tér vissza - hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben [???] + hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben A nyomkövetés megkönnyítésére a következõ példa egy hibát jelzõ JPEG-et állít elõ. example title @@ -759,7 +758,7 @@ /para para Az functionImageCreateFromPng/function üres stringgel tér vissza - hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben [???] + hiba esetén. Hibaüzenetet is ad, amit hibás linkként látunk a böngészõben A nyomkövetés megkönnyítésére a következõ példa egy hibát jelzõ PNG-t állít elõ. example title @@ -921,7 +920,8 @@ note para Ha nem bal felsõ és jobb alsó koordinátákat adsz meg, akkor lehal a - program, és a képbõl semmit sem fogsz látni!!![angol doksiba!] + program, és a képbõl semmit sem fogsz látni (lehet, hogy bug...)!!! + [angol doksiba!] /para /note /para @@ -1619,7 +1619,7 @@ karakter bal alsó sarkát). Ez egy különbség a functionImageString/function, függvénytõl, ahol az parameterx/parameter, parametery/parameter paraméterek az elsõ - karakter jobb felsõ [talán bal felsõ] sarkát határozzák meg. Ha nem + karakter jobb felsõ [vagy bal felsõ] sarkát határozzák meg. Ha nem érted, hogy miért úgy rajzol a függvény, olvasd a PostScript dokumentációját a betûkészletekkel meg a koordinátarendszerekkel kapcsolatban! @@ -1910,8 +1910,8 @@ /term listitem
[PHP-DOC] cvs: phpdoc / make_chm.README make_chm.bat make_chm.php make_chm_fancy.php
gobaMon Sep 3 12:05:03 2001 EDT Modified files: /phpdoc make_chm.README make_chm.bat make_chm.php make_chm_fancy.php Log: Moving to new file naming scheme introduced by Jouni with PDF generation: php_manual_LANG.chm Also many WS fixes in make_chm_fancy.php, more to come in make_chm.php Modifying all files to reflect the new file naming scheme Index: phpdoc/make_chm.README diff -u phpdoc/make_chm.README:1.7 phpdoc/make_chm.README:1.8 --- phpdoc/make_chm.README:1.7 Fri Aug 10 06:40:24 2001 +++ phpdoc/make_chm.README Mon Sep 3 12:05:03 2001 @@ -22,10 +22,10 @@ The html manual. You have two alternatives: a) Download the actual html manual from - http://snaps.php.net/manual/lang/ + http://www.php.net/download-docs.php and untar the distribution into a directory a) Build the html manual yourself using Jade and the other - tools needed (look into the README or README.win32 + tools needed (look into the README and/or README.win32 file to see how to build it yourself) The .chm manual generator files (from cvs.php.net): @@ -79,7 +79,7 @@ Put the html manual (~2100 files) under the subdir specified above in PHP_HELP_COMPILE_DIR (eg. html). -Now You need to decide what method to use (normal or fancy). +Now you need to decide what method to use (normal or fancy). The fancy manual .chm takes ~240k more space. This is not significant, as the .chm files are ~2.1Megs in size. @@ -94,7 +94,7 @@ This can take a while, the fancy manual takes ~6 minutes on a 750MHz Pentium with 128MB RAM, running Windows 98SE. -After this process, you will have manual-lang-date.chm in your language... +After this process, you will have php_manual_lang.chm... === The fancy design improvemenets and the .css file is based on @@ -104,4 +104,4 @@ Thomas Schöfbeck ([EMAIL PROTECTED]). Contact them or the phpdoc list ([EMAIL PROTECTED]) if you have any questions or suggestions... -Last modified $Date: 2001/08/10 10:40:24 $ \ No newline at end of file +Last modified $Date: 2001/09/03 16:05:03 $ \ No newline at end of file Index: phpdoc/make_chm.bat diff -u phpdoc/make_chm.bat:1.6 phpdoc/make_chm.bat:1.7 --- phpdoc/make_chm.bat:1.6 Sun Jun 24 12:14:40 2001 +++ phpdoc/make_chm.bat Mon Sep 3 12:05:03 2001 @@ -1,55 +1,55 @@ -@echo off - -rem !! Please read the make_chm.README file for information -rem !! about how to build a manual_lang.chm file. - -rem Path of the PHP CGI executable -set PHP_PATH=D:\progra~1\php404\php.exe - -rem Path of the Help Compiler command line tool -set PHP_HELP_COMPILER=D:\progra~1\helpwo~1\hhc.exe - -rem The language of the manual to compile -set PHP_HELP_COMPILE_LANG=en - -rem The source directory with the original DSSSL made HTML -set PHP_HELP_COMPILE_DIR=html - -rem The index file in this directory (manual.html or index.html) -set PHP_HELP_COMPILE_INDEX=index.html - -rem The directory, where the fancy files need to be copied -set PHP_HELP_COMPILE_FANCYDIR=fancy - -rem == -rem !DO NOT MODIFY ANYTHING BELOW THIS LINE ! -rem == - -echo. - -if a%1a == anormala goto skipfancy - -echo Now generating the fancy manual in %PHP_HELP_COMPILE_FANCYDIR% dir... -IF NOT EXIST %PHP_HELP_COMPILE_FANCYDIR%\NUL md %PHP_HELP_COMPILE_FANCYDIR% -%PHP_PATH% -q make_chm_fancy.php - -goto normal - -:skipfancy -set PHP_HELP_COMPILE_FANCYDIR= -echo Skipping fancy manual generation... - -:normal - -echo Now running the toc and project file generator script... -%PHP_PATH% -q make_chm.php - -echo Compiling the actual helpfile (manual-%PHP_HELP_COMPILE_LANG%-date.chm)... -%PHP_HELP_COMPILER% manual-%PHP_HELP_COMPILE_LANG%.hhp - -echo. -echo Cleaning up the directory -del manual-%PHP_HELP_COMPILE_LANG%.hh? - -echo Done! -echo. +@echo off + +rem !! Please read the make_chm.README file for information +rem !! about how to build a php_manual_lang.chm file. + +rem Path of the PHP CGI executable +set PHP_PATH=D:\progra~1\php404\php.exe + +rem Path of the Help Compiler command line tool +set PHP_HELP_COMPILER=D:\progra~1\helpwo~1\hhc.exe + +rem The language of the manual to compile +set PHP_HELP_COMPILE_LANG=en + +rem The source directory with the original DSSSL made HTML +set PHP_HELP_COMPILE_DIR=html + +rem The index file in this directory (manual.html or index.html) +set PHP_HELP_COMPILE_INDEX=index.html + +rem The directory, where the fancy files need to be copied +set PHP_HELP_COMPILE_FANCYDIR=fancy + +rem == +rem !DO NOT MODIFY ANYTHING BELOW THIS LINE ! +rem == + +echo. + +if a%1a == anormala goto skipfancy + +echo Now generating the fancy manual in
[PHP-DOC] cvs: phpdoc / .cvsignore
gobaMon Sep 3 12:05:47 2001 EDT Modified files: /phpdoc .cvsignore Log: Ignore the new php_manual_LANG.hh* files, and all *.chm files generated Index: phpdoc/.cvsignore diff -u phpdoc/.cvsignore:1.18 phpdoc/.cvsignore:1.19 --- phpdoc/.cvsignore:1.18 Mon Jul 9 18:37:51 2001 +++ phpdoc/.cvsignore Mon Sep 3 12:05:46 2001 @@ -11,6 +11,7 @@ *.rtf *.tex *.zip +*.chm .manual.xml Makefile bightml.xsl @@ -34,7 +35,7 @@ html.xsl htmlhelp.xsl makedoc -manual-*.hh* +php_manual_*.hh* manual.txt manual.xml missing.txt
[PHP-DOC] cvs: phpdoc / .cvsignore
gobaMon Sep 3 12:29:12 2001 EDT Modified files: /phpdoc .cvsignore Log: Also ignore the fancy directory Index: phpdoc/.cvsignore diff -u phpdoc/.cvsignore:1.19 phpdoc/.cvsignore:1.20 --- phpdoc/.cvsignore:1.19 Mon Sep 3 12:05:46 2001 +++ phpdoc/.cvsignore Mon Sep 3 12:29:12 2001 @@ -29,6 +29,7 @@ funclist.txt howto.dsl html +fancy html.cur html-locale.dsl html.dsl
[PHP-DOC] cvs: phpdoc / make_chm.php
gobaMon Sep 3 12:30:40 2001 EDT
Modified files:
/phpdoc make_chm.php
Log:
WS fixes, introduce the PEAR standards here, much more visible
to me, that what is done where
Index: phpdoc/make_chm.php
diff -u phpdoc/make_chm.php:1.13 phpdoc/make_chm.php:1.14
--- phpdoc/make_chm.php:1.13Mon Sep 3 12:05:03 2001
+++ phpdoc/make_chm.php Mon Sep 3 12:30:37 2001
@@ -7,272 +7,275 @@
$fancydir = getenv(PHP_HELP_COMPILE_FANCYDIR);
if (empty($fancydir)) {
- $fancydir = getenv(PHP_HELP_COMPILE_DIR);
+$fancydir = getenv(PHP_HELP_COMPILE_DIR);
}
$language = getenv(PHP_HELP_COMPILE_LANG);
$original_index = getenv(PHP_HELP_COMPILE_INDEX);
// header for index and toc
-$header =
- !DOCTYPE HTML PUBLIC \-//IETF//DTD HTML//EN\
- HTML
- HEAD
- meta name=\GENERATOR\ content=\PHP 4 - Auto TOC script\
- !-- Sitemap 1.0 --
- /HEAD
- BODY
- OBJECT type=\text/site properties\
- param name=\Window Styles\ value=\0x800227\
- /OBJECT
- UL
- ;
+$header = '
+!DOCTYPE HTML PUBLIC -//IETF//DTD HTML//EN
+HTML
+HEAD
+meta name=GENERATOR content=PHP 4 - Auto TOC script
+!-- Sitemap 1.0 --
+/HEAD
+BODY
+OBJECT type=text/site properties
+param name=Window Styles value=0x800227
+/OBJECT
+UL
+';
MakeProjectFile();
MakeContentFiles();
+/***/
+/* End of script lines, function follows */
+/***/
-/* end */
-
-/* functions */
-
-
+// Generate the HTML Help content files
function MakeContentFiles()
{
- global $fancydir, $language, $manual_title, $fancyindex, $indexfile,
$original_index, $header;
-
- $toc = fopen(php_manual_$language.hhc, w);
- $index = fopen(php_manual_$language.hhk, w);
-
- fputs($toc, $header);
- fputs($index, $header);
-
- $index_a = file($fancydir/$original_index);
- $ijoin = join(, $index_a);
- $ijoin = preg_replace(/[\r|\n]{1,2}/, , $ijoin);
-
- // print out the objects, that autoparsing wont find
- // some automation may be there in the future
-
- SiteMapObj($manual_title, $indexfile, , $toc, 21);
- IndexObj($manual_title, $indexfile, $index);
-
- if ($fancyindex) {
- preg_match('|CLASS=\title\ A NAME=\manual\ (.*)/A|U', $ijoin,
$match);
- if (empty($match[1])) {
- // fallback
- $match[1] = Table of Contents;
- }
- SiteMapObj($match[1], $original_index, , $toc, 21);
- IndexObj($match[1], $original_index, $index);
- }
-
- preg_match('|A HREF=preface.html (.*)/A |U', $ijoin, $match);
- if (empty($match[1])) {
- // fallback
- $match[1] = Preface;
- }
- SiteMapObj($match[1], preface.html, , $toc);
- IndexObj($match[1], preface.html, $index);
-
- fputs($toc, \n UL);
- preg_match('|A HREF=preface.html#about (.*)/A |U', $ijoin, $match);
- if (empty($match[1])) {
- // fallback
- $match[1]=About this Manual;
- }
- SiteMapObj($match[1], preface.html#about, , $toc);
- IndexObj($match[1], preface.html#about, $index);
- fputs($toc, /UL\n);
-
- // now autofind the chapters/subchapters
-
- $not_closed = 0;
-
- for ($i = 0; $i count ($index_a); $i++) {
- /* Chapters */
- if (ereg([IVX]+\.\ A, $index_a[$i])
!ereg(HREF=\ref\.[a-z0-9]+\.html, $index_a[$i+1])) {
-
- $new_list = 1;
- if ($not_closed == 1) {
- fputs($toc, \n /UL\n);
- }
-
- //preg_match (/([IVX]+)\. A/, $index_a[$i], $matches);
- //$chapter[nr] = $matches[1];
- preg_match(/HREF=\([a-z0-9-]+\.html)(\#[a-z0-9]+)?\/,
$index_a[$i+1], $matches);
- $chapter[html] = $matches[1];
- preg_match(/([^]+)/, $index_a[$i+2], $matches);
- $chapter[title] = $matches[1];
- SiteMapObj($chapter[title], $chapter[html], , $toc);
- IndexObj($chapter[title], $chapter[html], $index);
- }
-
- /* Sub chapters */
- elseif (ereg(([0-9]+|[IVXL]+|[A-Z])\.\ A, $index_a[$i])) {
- if ($new_list == 1) {
- $new_list = 0;
- $not_closed = 1;
- fputs($toc, \n UL\n);
- }
-
- //preg_match
[PHP-DOC] new naming scheme now with chm files
Hi! As Jouni introduced the new naming scheme for the PDF files, I have just modified the make_chm*.* files to use the php_manual_LANG.chm format. Please Derick, if you upload the files with the new names, inform us at [EMAIL PROTECTED], so we can change the scripts, or if you have the Karma, you can change it yourself. Also please delete the files with the old names if you can. I made some misc corrections in the generation process, although there are some errors. See the Language Reference/Classes and objects section, there are two errors: The chapter named :: is completely missing from the TOC [it is in the CHM, can be reached from other locations, just not listed in the left side tree] (but the regexp should find it IHMO) The other error is much triciker the The magic functions __sleep and __wakeup only shows up as __sleep. This is because a faulty detection of chapter titles. This detection works well in other places, and fails only here, as the title is multiline in the generated HTML, and the preg is only designed to handle one line titles. I'll correct this problems soon, if noone has time to do this. And again, Derick, please inform me or [EMAIL PROTECTED], if you upload with the new filenames. Thanks, Goba
Re: [PHP-DOC] Revision check, now working
Egon Schmid wrote: To make the story short. German translators don´t need a revision number or a revision comment. We need the diffs up to that date, when the original translator or maintainer leaved the project. It is impossible to make a script which tells a new translator he have to add, delete or to modify. I hope you understand this. It can happen, that we get a bug report about a misspelled word and if someone correct this, your revision system would fail. If you're talking in general, and that you can't explain/force newbies (how) to do it, it's fully OK to me. If this is meant categorical about all German translators, I disagree at least for myself. I wouldn't have written this script, if it wouldn't help. Since Goba has already done exhaustive explanations, I'll just explain why it's useful, even when I'm the only one using it: You already mentioned the problem with year old files which aren't maintained anymore, and I'm probably the only one who cares about it in German also for already assigned files (except one try from Mark, which got stopped), I had (and will have) a big work with them, because I have to do the whole file (As you know, array.xml, filetransfer.xml, install.xml, etc. aren't the smallest ones :). So I don't wanna lose much time with administering the files I've already done (currently 6 or 7, will be more). One script-call after the cvs-update, and I have a perfect overview about the actual status and priorities of all my files (yes, you can restrict the report also to a certain maintainer), and after one klick on the link I get immediatly the current diff directly from cvs.php.net (You can try it in de, there are already 3 files with comments) The time saved against opening Translators, searching my files, entering several links to the cvs per hand, etc. is much better used in translating/updating other things. So far the comment from only one German translator, for which it was even worth the time to write this script. Cu, Thomas
Re: [PHP-DOC] Revision check, now working
Hi Conni, It's a pity that Egon and you don't see the advantages, but you don't have to use it. But since Egon wrote no need, and not it's forbidden, at least I'll use it for my files. Cu, Thomas another german translator :) Cornelia Boenigk wrote: To make the story short. German translators don´t need a revision number or a revision comment. Basta;-) The chief has spoken. sorry, I couldn't resist;-) Conni a german translator
