[PHP-DOC] Portuguese (pt_BR) updates
I found how to update, so i have a copy from the time of cvs, very near to change to svn, so i make a revcheck in it and i am updating the docs, all the docs i will put svn revision 283790 as was told to me, so the files will be at first svn version, maybe need to update again on svn, but at last this will be a more easy work. I know that cvs do not work, i use it only to see the differences before change to svn and i am commiting on svn tree. will take some time, but now i started it. Fernando
[PHP-DOC] Updating the pt_BR translation
I want make the Brazilian(pt_BR) translation active again and work on it, and i will try find more people to help with. So i have some questions because those conversion from cvs to svn and if you can help me, i can continue on this work. 1. The way to see if a file needs update, stay as before? Using the svn version in the en file and puting it in the translated file as before with cvs? 2. What is the first version of the docs on svn? For me do a thing like get all the diffs since the migration and keep the docs updated from this point. 3. There is anyway to me know if a file was updated when this migration happen? If so, i can at last get all files that was fine, and the others i can translate one by one again as i have time and make then updated after this, i know that will be a great work, but for many time the translation was abandoned or with too little work, so there is many thing to update, i want preserve as much as i can and translate again what is necessary. I found now that i have a copy from the docs where it still on cvs, and a revcheck of it, so i can use it to know all the files that are not updated in the migration to svn 4. As the change to po will not happen too soon, i will not wait for it. And when the online editor is working, will be much easy to translate and to find people to help me with this, as a example as this will help, you can be anywere and direct from a browser help without the need to setup anything on your pc, if you have 5 free minutes you translate a file :) 5. The revcheck is not working for me, at last when i checkout using the module to get all necessary files, maybe this mess the layout that revcheck expects. Fernando Correa da Conceição www.jaguaribe.net
Re: [PHP-DOC] Updating the pt_BR translation
Nilgün Belma Bugüner escreveu: Pazar 09 Ağustos 2009 21:56 sularında, Fernando Correa da Conceição şunları yazmıştı: I want make the Brazilian(pt_BR) translation active again and work on it, and i will try find more people to help with. So i have some questions because those conversion from cvs to svn and if you can help me, i can continue on this work. 1. The way to see if a file needs update, stay as before? Using the svn version in the en file and puting it in the translated file as before with cvs? cd phpdoc/en $ svn propget cvs2svn:cvs-rev preface.xml 1.36 2. What is the first version of the docs on svn? For me do a thing like get all the diffs since the migration and keep the docs updated from this point. 1.36 is the CVS revision number assigned to the file transferred from the SVN repository. 3. There is anyway to me know if a file was updated when this migration happen? $ svn log preface.xml r283791 | nilgun | 2009-07-11 08:24:47 +0300 (Sat, 11 Jul 2009) | 1 line fixed properties ---[deleted] keywords: 2009-07-11, nilgun, fixed properties I hope this helps. -- Nilgün Sorry but i still do not understand how what you said will help me, let me explain in another way. There is a tool that makes the same work as revcheck.html or make it work now, because i can not, it do not find the pt_BR and tell that is an invalid translation. Fernando
Re: [PHP-DOC] PO files progress
pedram salehpoor escreveu: Hi I wanted to know how the changes for PO files are progressing and if there is anything that I can do to ease the change? Regards. Pedram Salehpoor +1 Fernando.
[PHP-DOC] The present and future of translations
Some questions: 1. How we update the files now? The files that are updated with this change to svn is simple, keep updating then. And for the files that are outdated in cvs? The change to pot: - Create a wiki page about it - There is some way to edit it online as will be posible with xml with the new online editor being developed on gsoc? A way to edit online will make more easy for translation(and make more peolple participate), do not matter the format we work. Fernando.
Re: [PHP-DOC] Re: [HEADSUP] Call for help
Philip Olson escreveu: snip With the new editor online why change to po? More work lost and more markup changes? Sorry but each time that en make a change like this is less people on translation, and days of work only to update to a new system. Will be more one system to mantain, more time lose on doc build, phd did a great work on reducing it and making it simple, now increase it again and make a lot more comples again? So: will be a en file, this file is converted to po, i have to see the diffs in en po, do it in pt_BR, convert my file again to xml, build it. If there is a kind of auto update tool like the used for po will break many langs, po is usefull for short messages for text is horrible. At last make a option for everyone who want keeps working direct on xml files and not on pot. Fernando. Okay, I'll summarize why I feel a gettext approach is good. If I misunderstand the situation then _please_ say so as I am not an expert on translations. The bottom line is our current system is archaic, broken, and in need of a major overhaul. However, we don't need to rush into anything but I figure using po files would be a good base. So: - Today a markup change to EN easily breaks translations The po will resolve this? Will have any kind of autoupdate for each translation ? - Today adding a new section (any id) likely breaks translations Same as above? - Many tools exist for editing po files Many tools exist for xml files too, and everyone working with php must have some of then - Many tools offer statistics for po files And this will make the translations better if we know how many sentences in a file is transtaled or uptodate? - I presume it's easier to do things like: --- if file x is 80%+ translated and up to date, build, else show EN There is not parcial translations, and if there is wrong. If the file is not updated some revisions do not build it, is more simple than a parcial translated file or worst, a file with some sentences in both languages --- Or, fine tune it further, paragraph by paragraph (wise? weird?) Will do as same as above, a paragraph in each language? The po update will do this because it is done for simple sentences, not for texts - Translators can focus on translating and not DocBook or markup --- Ex: As of one minute ago, 5/11 of our 'active' translations are not building. I doubt any of the 20 others do at all. What markup the translator need to know? Only hot to work with xml without break it, translator do not add tags and do not remove then. - Better translation tools are available with po files, like for TM and CAT - Other people use it, so maybe it's the cool thing to do - Since other people do it, we can steal their tools and ideas Our current system is not working. We have two translations that can be considered fully up to date (JA and FR). And now to summarize reasons why we should not use PO files: - Longer build time for docs - Must learn something new - Must create new tools that help deal with them - Deal with contextual issues in PO files A few problems we must solve: - Most translations are dead or have little life -- yet the global PHP community is huge - Translators shouldn't have to worry about Markup (DocBook or otherwise) - Changes/additions to EN shouldn't break translations - Today we require CVS Revision numbers, which won't exist in SVN (CVS-SVN is coming this month) Rant: I'm baffled by how little attention the topic of translations receives in the Open Source world. It's treated like an afterthought when really it should be central to everything. All efforts appear as hacks including the use of po files for a manual. This is sad. Or, did I miss the memo? /Rant. So to reply specifically to Fernando's concerns: Although some markup still exists within translated strings (in the PO files), I figure typically translators building the translation won't be necessary. We could setup a system to do the build and yell at the translations list when it's broken, or something similar, but point is I don't see this as a block for translations. I imagine a translator opening a PO file and translating very fast and not worrying about much else. Also, I don't think having multiple options (XML or PO) for translators is worth the effort. What do people think? It's now or never. Questions? Suggestions? Other ideas? Regards, Philip Do as you want. But because all that markup and changes like this many peolple have left the pt_BR translation. Was days of work only to make it build with livedocs., more work with phd(this was good) and now the po, more tools, more work, more one thing to setup, more thing to learn === less translators. Fernando.
Re: [PHP-DOC] Re: [HEADSUP] Call for help
Philip Olson escreveu: On Jul 5, 2009, at 2:53 PM, G. T. Stresen-Reuter wrote: On Jul 5, 2009, at 2:57 PM, Peter Beverloo wrote: With the documentation moving to PO files soon (as well as changes around the PhD editor GSoC project) I follow this list pretty closely but I must have missed this (rather important) news item. When will the documentation move to PO files? How will this change the translation process and source files? Is this move documented somewhere? In short, is there an other list where such decisions are made that I'm unaware of? Several translation related discussions have taken place on the subject although typically they have been short threads. The English documentation process will not change as PO files are only used by translations. The process has been poorly documented (by me) but is moving forward. It's a bit chaotic especially considering the rush to get it done before the project moves to SVN but here are a few recent threads on the topic: - http://markmail.org/thread/iqxkiekmvz6h43lt - http://markmail.org/thread/kidqiimuglh2tmfh - http://markmail.org/message/fduqvora3lef4cit A test repository with PO files are in CVS although they are only English (POT) and Japanese as it's purely for testing purposes: - http://cvs.php.net/viewvc.cgi/phpdoc-po/ How PO files will be managed is still up in the air but we're in the midst of testing out several systems including: - http://www.transifex.net/projects/php/ - http://translate.php.net/ Neither of the above work today as our project appears too large for transifex.net to handle (today, they are discussing how to solve this) but they offer a system that could coincide with whatever else we choose as it offers help from an additional translation community. And our Pootle setup (at translate.php.net) is sketchy with a strange bug (thanks to me) but once Michael has time he'll look into it as my sysadmin skills sit right around null. So that's the situation. Given the mere size of this move, the SVN rush, and my lack of knowledge (but it's interesting to learn this) I'm afraid it won't go smoothly. All help is desired, as are questions and/or answers. Regards, Philip With the new editor online why change to po? More work lost and more markup changes? Sorry but each time that en make a change like this is less people on translation, and days of work only to update to a new system. Will be more one system to mantain, more time lose on doc build, phd did a great work on reducing it and making it simple, now increase it again and make a lot more comples again? So: will be a en file, this file is converted to po, i have to see the diffs in en po, do it in pt_BR, convert my file again to xml, build it. If there is a kind of auto update tool like the used for po will break many langs, po is usefull for short messages for text is horrible. At last make a option for everyone who want keeps working direct on xml files and not on pot. Fernando.
Re: [PHP-DOC] PhD Improvements (Plugin System) - Status Report 5
Moacir de Oliveira escreveu: Hi Fernando, You forgot to add a CC to the lists (g...@lists.php.net mailto:g...@lists.php.net, phpdoc@lists.php.net mailto:phpdoc@lists.php.net). Its better because all the community will see our discussion. congrats, --Moacir I forgot that I must reply to all and not only Reply I see you talking about php and pear, anything about php-gtk? What is exactly a phd plugin? If I write one, I can use phd to process a book with a xml markup that is not same as phpdoc? If yes, I want work on one to php-gtk-doc. Where I can get the sources for phd that is the one you are working? I have a cvs acount. Fernando
Re: [PHP-DOC] Commit freeze (Merging from REF_STRUCT_DEV)
One last thing about this. We need change the revcheck to ignore entities.reference.xml as it do for functions.xml Fernando.
[PHP-DOC] Comments on uodbc/book.xml
What is this comment on uodbc/book.xml?
!-- {{{ preface --
I think that is something related to folding, can be vim? I ask this
because I do not want to update the translation later only to remove
this kind of comment.
Fernando.
Re: [PHP-DOC] Commit freeze (Merging from REF_STRUCT_DEV)
Hannes Magnusson escreveu: On Dec 10, 2007 1:48 PM, Fernando Correa da Conceição [EMAIL PROTECTED] wrote: Philip Olson escreveu: On Dec 9, 2007, at 11:52 AM, Hannes Magnusson wrote: Hi all I will be merging from the REF_STRUCT_DEV branch as of tomorrow and would therefor like to request a total commit freeze to phpdoc/ as of December 10th, 15:00 UTC (tomorrow, Monday) until further notice. Translations are not affected. In fact, translators are encouraged to sync their translations while this freeze is in affect. It is a lot of work (~180 extension references) so I don't expect the docs to build or even validate for the next few days until everything has been merged. To make this process as painless as possible for our translators I'll do my best to merge only one extension at a time and taking notes of any weirdness that may occur. The biggest changes, as you should be aware of by now, are the reference pages and renamed files (OO extensions). There are virtually no content changes, only refactoring and minor markup upgrades. Note: Even after the merge _no_ translations will validate. Unfortunately there is pretty much nothing we can do about that. I am hoping to push out these changes onto phpweb somewhere around new year, it would be great if most translations have been brought in sync by that time. Hello all, Hannes, have fun doing the merge! And again sorry translators... if you have questions or desire help then please speak up. If this is necessary. I have a simple request, if is possible. There is a server that builds the docs using the phd. There is a way to make it send a mail when a build fails? If this is possible, will be good, as we will know that some change breaks the build and we can try to fix it. The build fails, guaranteed, if the translation is not up2date with the reference.xml split due to duplicated IDs. These duplicated IDs are caused by the new root/container file, book.xml (since all extensions are now books), which includes a setup.xml chapter file (containing the installation+configuration+requirements sections). Then the reference.xml file will be included which (unless it is up2date) again defines the same sections, causing duplicated IDs. Furthermore, the constant sections are now chapters, not sections and the document will therefor not validate. So: 1. There is a new file, book.xml. This is the main file for each extension. 2. There is a new file, setup.xml. It have howto install and setup a extension. 3. The reference.xml will contain samples and this kind about a extension. The setup and what is an extension will go to the files above. 3. The file functions.xml is now entities.functions.xml. Is a simple rename or there is other change? Quick'n'dirty build fix is would therefore be possible by simply removing all reference.xml and either upgrade the root elements in constants.xml to chapter or simply remove the file. We do send out automatic build failure mails[1], when the CHM versions are built (once a week). However, since the English build will be messed up for few days all translations will be too. There is therefor no point in spamming the lists with these mails and have they therfore been disabled for a while. And a dumb question. This merge is from a branch to head. We keep working(translating) on head, sure? Indeed. I duly recommend translators blindly sync their translations with the English version right away. Then when everything appears to be in sync try to validate it and fix any errors that come up. -Hannes [1] With the exception of the pt-br translation, as there was/is a typo(I assume) in the mailinglist name causing the mail to be sent out to non-existing-mailinglist. I will look at this. The mailing list is not [EMAIL PROTECTED] ? Fernando I however get CC'ed all build failures and have have fixed them all when they occur :]
Re: [PHP-DOC] Found the errors
Simion Onea escreveu: -Original Message- From: Hannes Magnusson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 27, 2007 12:04 PM To: Simion Onea Cc: PHPdoc Subject: Re: [PHP-DOC] Question about the tools On Nov 27, 2007 7:41 AM, Simion Onea [EMAIL PROTECTED] wrote: Hi! Could you please tell me if I am correct: First I run autoconf. (no errors/warnings) Then I run ./configure --with-lang=ro. And it says that I have missing ids. So I cannot expect that make test will pass. Am I correct? I don't think make test works anymore, but since the missing IDs are detected at ./configure time they are replaced with ??? to fix the build. Meaning: make test_xml works fine - even with missing IDs. -Hannes Oh, I found the errors! They went to PHP's error log that I configured. A lot of IDs are missing (about 40). Probably because the majority of files are not translated. But I thought they will be taken ftom the English tree. What can I do? I just wanted to build the Romanian manual as it is. Regards, Simion. Missing ids is not that a file is not translated. Is about outdated files, files that need update. Some id change or is added on a en file and this file is not updated, this will make a missing id, because the id exists on en(and can be used in other part of the manual) but do not exist in ro, because the translated version do not have it. So, to take care of missing ids, update the files where they are. And the manual build without any error with/without missing ids. The build system take care of this. Fernando Correa da Conceição
Re: [PHP-DOC] fixing our translations
(without the xml is uselles for us), but many persons did some work on it, simple because it is easy and take little time to work, you do not need to install and setup nothing. By example, let who have a cvs account commit direct from the web and all others, save the translations in a kind of sandbox, so someone with a cvs account can review and commit it latter. Fernando Correa da Conceição Regards, Philip [1] http://doc.php.net/php/revcheck.php
Re: [PHP-DOC] Entity reftitle.returnvalues
Felipe Pena escreveu: Hello, In Brazilian portuguese translation the value of entity reftitle.returnvalues shouldn't be 'titleValor retornado/title' instead of 'titleValores de retornado/title'? As I reported in http://bugs.php.net/bug.php?id=42990 Fixed in cvs. Thanks, and keep with this help!
Re: [PHP-DOC] Two entities in pt_BR translation
Felipe Pena escreveu: The following entities is incorrect: !ENTITY reftitle.errors 'titleErros/Excessões/title' !ENTITY ReservedConstants Constantes Predefinidas I suggest: Excessões - Exceções Predefinidas - Pré-definidas Done! Fernando.
Re: [PHP-DOC] EN-Revision comments Vs Docbook revision attributes
Hannes Magnusson escreveu: Hello all Was there any specific reason why this EN-Revision comment magic was chosen over the Docbook revision attribute? As I see it we could safe our translators _alot_ of work by manually bumping revision whenever the changes done in the en docs need re-translation. This would mean that all the WS, typo, grammar and other English specific bugs won't bump revision = nothing for translators to fix, they shouldn't be forced to updated some tags. The only argument against it (I could find) is more work for en doc writers. Heh? Right. That argument is so selfish that if anyone so much as mentions it I'll hunt the person down and throw snowballs at him :) Choosing when to bump revision and when not takes under 2seconds. Compared to the 5seconds[1] it takes _every_ translator to figure out if there was any real change or if he just needs to bump his EN-Revision (another few seconds)... This will also allow us to more accurately determine if a translation is really out of date or not. What do you guys think? [1] Locating and opening the commit. Read the commit message and then review the commit... hmm. That is probably more than 5secs.. -Hannes As an translator, a big +1 for this. Fernando Correa da Conceição.
[PHP-DOC] Help with the makefile for phpdoc
I have an error on the makefile. I do: ./configure --with-lang=pt_BR and after this make But it gives me an error: Generating the manual...make: no: Comando não encontrado make: ** [.manual.xml] Erro 127 which means no: command not found This is on Debian Etch. Thanks for any help. Fernando Correa da Conceição.
Re: [PHP-DOC] a request to become editor
+1 from me. Now when we have have some request we know who is the person to talk! Philip Olson escreveu: Hello doc friends, We again could use an editor that is responsible for tackling our administrative tasks. It's been well over a year since Gabor stepped down and having a replacement to continue his legacy feels like a good idea. We've accomplished a lot since but are missing the other things being done. I humbly request taking over as editor and would be sure (and required) to complete the following tasks: * Manage and prioritize (and use) the TODO * Overhaul the dated doc HOWTO * Ensure that scripts/check_phpdoc/ is implemented, livedocs too * Document our build system and scripts/ so people understand how the magic happens * Write less documentation, but spend time finding people to write documentation * Follow the mailing lists and ensure that all questions receive responses * Discuss and propose an updated and manageable credits system * Manage docweb and encourage its use * Write monthly doc updates to the internals list * Make our dream of submissions|patches via the browser come true * Have the new doc style fully implemented in 2007 * Be diplomatic * Manage doc related CVS karma * Monitor QA and encourage non-native (but decent) English speakers to commit to en/ * Create topics for discussion, like our user notes and dead translations * Promote the ideas described in this book: http://producingoss.com/ * And in this talk: http://video.google.com/videoplay?docid=-4216011961522818645 The key is to have someone designated to do certain tasks, tasks that aren't always the most fun to perform. The title editor is not something to take lightly and as editor I know personally I'd forget less and do more. And although my duties with the php.net project have spread into many areas, the PHP Manual is my #1 priority. And it needs more love. I commit to at least one year and at that time we should reevaluate and hopefully we'll be ready to assign all tasks to individual members. I don't feel we're there yet as most of us have grown old and spend less time here now, but we'll get there if we want to. I hope everyone is happy with this as it means a fellow member (the old bearded guy) is promising and committing consistent focused time but if not then please feel free to speak up. Yay or Nay? Regards, Philip Olson
Re: [PHP-DOC] BUild
Derick Rethans escreveu: On Fri, 20 Oct 2006, Lajos Cseppentõ wrote: How can I run a build on the Hungarian documentation? Mention it here... and I start a build. It is running now, and will take a bit more than a day. regards, Derick And one for portuguese (pt_BR) ? Thanks
[PHP-DOC] Patch to build only one file
Hi!
I make two php scripts and a modification on
Makefile.in, and with this you can build the html for one function or a chapter,
by example:
make
file=./en/reference/mysql/functions/mysq-query.xml
Build the html only for this function
and
make
file=./en/reference/mysql/reference.xml
Build all mysql functions.
This is for who write/translate the docs as you can
see your changes without build the entire manual, which can take one hour or
more, by example, with this i generate all mysql functions in 3
minutes.
I need a help with it, in process I generate a .tmp
file and I want to delete it after use, but I´m good with makefiles, so I need
this:
if file != "manual.xml" then delete
file.
Instructions:
1. Apply the patch on Makefile.in and place the
scripts on /scripts
2. ./configure
3. php ./scripts/geraentidades.php
This creates a filewith
all entities(.ent files) that i include later on .tmp files. You need run this
this only after configure or when a .ent file changes.
4. Use make as show above.
Note that if you don´t use file=./ it don´t
change anything on build process.
Patch to Makefile.in
Index:
Makefile.in===RCS
file: /repository/phpdoc/Makefile.in,vretrieving revision 1.146diff -u
-r1.146 Makefile.in--- Makefile.in3 Jan 2004 12:32:15
-1.146+++ Makefile.in10 Jan 2004 17:08:38 -@@ -21,6
+21,12 @@all: html+ifdef
file+ext=.tmp+else+file=manual.xml+endif+# {{{
variables[EMAIL PROTECTED]@@@ -167,7 +173,8
@@html/index.html: manual.xml $(HTML_DEPS)@test -d
html || mkdir html$(PHP) -q
$(scriptdir)/rtlpatch/hackmanuallang.php $(LANGDIR)-$(JADE) $(CATALOG)
-d $(HTML_STYLESHEET) -V use-output-dir -t sgml $(XMLDCL)
manual.xml+$(PHP) -q $(scriptdir)/compila.php
$(file)+$(JADE) $(CATALOG) -d $(HTML_STYLESHEET) -V use-output-dir -t
sgml $(XMLDCL) $(file)$(ext)$(PHP) -q
$(scriptdir)/html_syntax.php html html/$(PHP) -q
$(scriptdir)/rtlpatch/hackmanuallang.php
en$(HACK_RTL_LANGS_PAGES)
geraentidades.php.in
?php
/**
** by Fernando Correa da Conceição fernandoc at
php.net
**/$saida="!DOCTYPE book PUBLIC
\"-//OASIS//DTD DocBook XML
V4.1.2//EN\"
\"./dtds/dbxml-4.1.2/docbookx.dtd\"
[";$lista=array("./entities/global.ent","./entities/file-entities.ent","./entities/version.ent",
"./@LANG@/language-defs.ent","./@LANG@/language-snippets.ent",
"./en/language-defs.ent","./en/language-snippets.ent");foreach($lista as
$filename) { if (!$handle = fopen($filename, 'r'))
{ echo "Error, can´t open
($filename)";
exit; }
$arquivo=file_get_contents($filename);
$saida.=$arquivo."\n";}$saida.="\n]";$filename="./entidades.ent";if
(!$handle = fopen($filename, 'w')) { echo "Error, can´t open
($filename)"; exit;}if (!fwrite($handle, $saida))
{ print "Error, can´t write
($filename)"; exit;}
?
*
compila.php
?
/**
** by Fernando Correa da Conceição fernandoc at
php.net
**/$arquivo=$argv[1];if($arquivo ==
"manual.xml")
exit;$linhas=file($arquivo);$entidades=file_get_contents("entidades.ent");$linhas[1].=$entidades."\nbook\narticle";$saida=join("",$linhas);$saida.="\n/article\n/book";$filename=$argv[1].".tmp";if
(!$handle = fopen($filename, 'w')) { echo "Error, can´t open
($filename)"; exit;}if (!fwrite($handle, $saida))
{ print "Error, can´t write
($filename)"; exit;}
?
Fernando Correa da ConceiçãoICQ
168518047http://manualphp.sourceforge.netParticipe
da Tradução do Manual do PHP
Re: [PHP-DOC] Patch to build only one file
Sorry.make file=./en/reference/mysql/functions/mysq-query.xml make file=./en/reference/mysql/functions/mysql-query.xml
[PHP-DOC] (New Version) - Patch to build only one file
I build a new version with the ideas from Goba
(Thanks!), now there is only one script in php and it is in
english.
This is more simple, so, to use:
Apply the path to Makefile.in
Add the script to /scripts
./configure
make file=file to generate, example:
make
file=./en/reference/mysql/functions/mysql-query.xml
Index:
Makefile.in===RCS
file: /repository/phpdoc/Makefile.in,vretrieving revision 1.146diff -u
-r1.146 Makefile.in--- Makefile.in3 Jan 2004 12:32:15
-1.146+++ Makefile.in10 Jan 2004 19:35:29 -@@ -21,6
+21,12 @@all: html+ifdef
file+buildfile=addentities.xml.tmp+else+buildfile=manual.xml+endif+#
{{{ variables[EMAIL PROTECTED]@@@ -167,7 +173,8
@@html/index.html: manual.xml $(HTML_DEPS)@test -d
html || mkdir html$(PHP) -q
$(scriptdir)/rtlpatch/hackmanuallang.php $(LANGDIR)-$(JADE) $(CATALOG)
-d $(HTML_STYLESHEET) -V use-output-dir -t sgml $(XMLDCL)
manual.xml+$(PHP) -q $(scriptdir)/addentities.php
$(file)+$(JADE) $(CATALOG) -d $(HTML_STYLESHEET) -V use-output-dir -t
sgml $(XMLDCL) $(buildfile)$(PHP) -q
$(scriptdir)/html_syntax.php html html/$(PHP) -q
$(scriptdir)/rtlpatch/hackmanuallang.php
en$(HACK_RTL_LANGS_PAGES)
***
addentities.php.in
?php/*** by Fernando Correa da
Conceição fernandoc at php.net** This script let you compile
only one file. Use:* make file=filename* example:* make
file=./en/reference/mysql/functions/mysql-query.xml* to all functions from a
extension* make
file=./en/reference/mysql/reference.xml*/$file=$argv[1];// if we are
working with the default rule, exit// TODO: maybe do this on
Makefileif($file == "") exit;
$lines=file($file);
// this is the beginning from
manual.xml.in$header = endblock!DOCTYPE book PUBLIC
"-//OASIS//DTD DocBook XML
V4.1.2//EN"
"@srcdir@/dtds/dbxml-4.1.2/docbookx.dtd" [
!-- Add translated specific definitions and
snippets --!ENTITY % language-defs SYSTEM
"@srcdir@/@LANGDIR@/language-defs.ent"!ENTITY % language-snippets
SYSTEM "@srcdir@/@LANGDIR@/language-snippets.ent"
%language-defs;%language-snippets;
!-- Fallback to English definitions and
snippets (in case of missing translation) --!ENTITY %
language-defs.default SYSTEM
"@srcdir@/en/language-defs.ent"!ENTITY % language-snippets.default
SYSTEM "@srcdir@/en/language-snippets.ent"
%language-defs.default;%language-snippets.default;
!-- phpweb entities - autogenerated!
--!ENTITY % phpweb.entities SYSTEM
"entities/phpweb.ent"
%phpweb.entities;
!-- All global entities for the XML files
--!ENTITY % global.entities SYSTEM
"@srcdir@/entities/global.ent"
!-- These are language independent
--!ENTITY % build.version SYSTEM
"entities/version.ent"!ENTITY % file.entities
SYSTEM "entities/file-entities.ent"
!-- Include all external DTD parts defined
previously
--%global.entities;%file.entities;%build.version;
!-- Autogenerated missing entites and IDs to
make build work --!ENTITY % missing-entities SYSTEM
"entities/missing-entities.ent"%missing-entities;
!ENTITY missing-ids SYSTEM
"entities/missing-ids.xml"]endblock;
// here a add the beginning from
manual.xml.in// and the tags book and article to make jade
happy$lines[1].="\n".$header."\nbook\narticle";
// join all again and add closing tags for book and
article$output=join("",$lines);$output.="\n/article\n/book";
// generate a temp file with all
things$saveto="./addentities.xml.tmp";if (!$handle = fopen($saveto,
'w')) { echo "Error, can´t create/open
($saveto)"; exit;}if (!fwrite($handle, $output))
{ print "Error, can´t write
($saveto)"; exit;}
?
Fernando Correa da ConceiçãoICQ
168518047http://manualphp.sourceforge.netParticipe
da Tradução do Manual do PHP
[PHP-DOC] tidy and windows.
On tidy documentation, say it works on php4, so I go to pecl, but there is not a dll for windows, only source for linux. So, this work on windows? If no the docs must say this. Fernando Correa da ConceiçãoICQ 168518047http://manualphp.sourceforge.netParticipe da Tradução do Manual do PHP
[PHP-DOC] Serious bugs on tidy functions names!
I use windows ME. The names with :: are invalid under windows, I don´t know in ntfs, but in FAT filesystem is. So when I update my copy from manual I got many messages like this: cvs95 update: cannot write en/reference/tidy/functions/tidy-node::attributes.xml: No such file or directory cvs95 update: cannot write en/reference/tidy/functions/tidy-node::children.xml: No such file or directory So this files does not exist for me. Fernando Correa da ConceiçãoICQ 168518047http://manualphp.sourceforge.netParticipe da Tradução do Manual do PHP
Re: [PHP-DOC] commit files with the web interface
-Mensagem Original- De: Nuno Lopes [EMAIL PROTECTED] Para: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Enviada em: domingo, 19 de outubro de 2003 15:52 Assunto: [PHP-DOC] commit files with the web interface Hello, I need your oppinion about the way how commits will work in the web interface to translate the manual. There was an idea to solve the problem of being always changing CVS dir with the user's information. The solution would be to have just a CVS account (that hot solution) and all commits would be done by the admin of the project. I'll explain: A translator would translate a file. Then, that file would be marked as 'to-review'. Then, the admin would read the file, and make any changes (if necessary), and the file would be marked as 'to-commit'. At the end of day (throught a cron job) an update script would run and checkout any changes to files and would commit/add the new translations. With this solution, we would have better quality translations and we would have just one CVS account for each project. This is better than previous in use only one acount and I person view the files before commit. More one sugestion, the script at cron do a make test before commit to make sure the manual compiles. Any comments? Nuno Lopes
[PHP-DOC] Commit messages not send email
Hi! Recent commit messages with many files are not sending mail to list with log message and the diff. This can be due the cvs server is without free space or little!! A example: One of pt_BR translators send /reference/calendar and /reference/calendar/functions in wrong place to en. This don´t send the email with commit. Later in same day I correct it by replacing the pt_BR files with the en files. This don´t send the email with commit too. Later they send same files to /pt_BR/reference, the rigth place and the mail message was send. The reason of this may be: on wrong commits ou got the file size *2(all the en and pt_BR version) and on add only one once(the pt_BR file). This could be a serious trouble and someone may look at this! Thanks. Fernando.
[PHP-DOC] cvs: phpdoc /en/reference/array/functions array-udiff-uassoc.xml
fernandoc Fri Oct 10 01:08:09 2003 EDT Modified files: /phpdoc/en/reference/array/functionsarray-udiff-uassoc.xml Log: Fix wrong ID # Don´t you use make test? Index: phpdoc/en/reference/array/functions/array-udiff-uassoc.xml diff -u phpdoc/en/reference/array/functions/array-udiff-uassoc.xml:1.1 phpdoc/en/reference/array/functions/array-udiff-uassoc.xml:1.2 --- phpdoc/en/reference/array/functions/array-udiff-uassoc.xml:1.1 Thu Oct 9 03:28:40 2003 +++ phpdoc/en/reference/array/functions/array-udiff-uassoc.xml Fri Oct 10 01:08:09 2003 @@ -1,7 +1,7 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- !-- splitted from ./en/functions/array.xml, last change in rev 1.14 -- - refentry id=function.array-udiff-assoc + refentry id=function.array-udiff-uassoc refnamediv refnamearray_udiff_uassoc/refname refpurposeComputes the difference of arrays with additional index check. The data is compared by using a callback function. The index check is done by a callback function also/refpurpose
[PHP-DOC] No CVS message on commit
I don´t know exact how many files I send(all files under /reference/calendar) but the email with commit message was not send Fernando Correa da ConceiçãoICQ 168518047
[PHP-DOC] cvs: phpdoc /en/reference/msql/functions msql-connect.xml
fernandoc Sat Sep 6 21:59:06 2003 EDT Modified files: /phpdoc/en/reference/msql/functions msql-connect.xml Log: et - and Index: phpdoc/en/reference/msql/functions/msql-connect.xml diff -u phpdoc/en/reference/msql/functions/msql-connect.xml:1.3 phpdoc/en/reference/msql/functions/msql-connect.xml:1.4 --- phpdoc/en/reference/msql/functions/msql-connect.xml:1.3 Thu Feb 13 21:48:51 2003 +++ phpdoc/en/reference/msql/functions/msql-connect.xml Sat Sep 6 21:59:06 2003 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- !-- splitted from ./en/functions/msql.xml, last change in rev 1.2 -- refentry id=function.msql-connect refnamediv @@ -46,7 +46,7 @@ /para para See also - functionmsql_pconnect/function et + functionmsql_pconnect/function and functionmsql_close/function. /para /refsect1
[PHP-DOC] A question in sqlite_create_function
I was translating and don´t understand this: line 90 para This example will call the functionmd5/function on each literalfilename/literal column in the database and return the result into parameter$rows/parameter /para This database is not table? If I have a database with two tables, in example two columns named filename, one in each table. It will affect both or only the table i query? line 69 parameter$rows/parameter This is not wrong? parameter is not only for functions parameters? Thanks! Fernando Correa da Conceição -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/sqlite/functions sqlite-fetch-array.xml
fernandoc Sun Aug 3 13:15:26 2003 EDT Modified files: /phpdoc/en/reference/sqlite/functions sqlite-fetch-array.xml Log: Add a missing revision tag Index: phpdoc/en/reference/sqlite/functions/sqlite-fetch-array.xml diff -u phpdoc/en/reference/sqlite/functions/sqlite-fetch-array.xml:1.4 phpdoc/en/reference/sqlite/functions/sqlite-fetch-array.xml:1.5 --- phpdoc/en/reference/sqlite/functions/sqlite-fetch-array.xml:1.4 Sun Jul 6 00:43:08 2003 +++ phpdoc/en/reference/sqlite/functions/sqlite-fetch-array.xml Sun Aug 3 13:15:26 2003 @@ -1,4 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? +!-- $Revision: 1.5 $ -- refentry id=function.sqlite-fetch-array refnamediv refnamesqlite_fetch_array/refname -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/ibase/functions ibase-connect.xml
fernandoc Sun Jul 27 13:21:23 2003 EDT Modified files: /phpdoc/en/reference/ibase/functionsibase-connect.xml Log: Add a note about character set Index: phpdoc/en/reference/ibase/functions/ibase-connect.xml diff -u phpdoc/en/reference/ibase/functions/ibase-connect.xml:1.4 phpdoc/en/reference/ibase/functions/ibase-connect.xml:1.5 --- phpdoc/en/reference/ibase/functions/ibase-connect.xml:1.4 Mon Jan 20 21:39:20 2003 +++ phpdoc/en/reference/ibase/functions/ibase-connect.xml Sun Jul 27 13:21:23 2003 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/ibase.xml, last change in rev 1.2 -- refentry id=function.ibase-connect refnamediv @@ -79,6 +79,15 @@ para The optional parameterrole/parameter parameter was added in PHP 4.0.0 and is functional only with InterBase 5 and up. + /para +/note +note + para + If you get some error like arithmetic exception, numeric overflow, or string truncation. Cannot + transliterate character between character sets (this occurs when you try use some character + with accents) when using this and after + functionibase_query/function you must set the character set(ie ISO8859_1 or your current + character set). /para /note para -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/sqlite/functions sqlite-open.xml
fernandoc Sat Jun 21 15:58:04 2003 EDT
Modified files:
/phpdoc/en/reference/sqlite/functions sqlite-open.xml
Log:
Fixing example. sqlite-query need two args.
Index: phpdoc/en/reference/sqlite/functions/sqlite-open.xml
diff -u phpdoc/en/reference/sqlite/functions/sqlite-open.xml:1.5
phpdoc/en/reference/sqlite/functions/sqlite-open.xml:1.6
--- phpdoc/en/reference/sqlite/functions/sqlite-open.xml:1.5Fri Jun 20 15:31:15
2003
+++ phpdoc/en/reference/sqlite/functions/sqlite-open.xmlSat Jun 21 15:58:04
2003
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.5 $ --
+!-- $Revision: 1.6 $ --
refentry id=function.sqlite-open
refnamediv
refnamesqlite_open/refname
@@ -44,9 +44,9 @@
![CDATA[
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
- sqlite_query('CREATE TABLE foo (bar varchar(10))');
- sqlite_query(INSERT INTO foo VALUES ('fnord'));
- $result = sqlite_query('select bar from foo');
+ sqlite_query($db,'CREATE TABLE foo (bar varchar(10))');
+ sqlite_query($db,INSERT INTO foo VALUES ('fnord'));
+ $result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/gettext configure.xml
fernandoc Sat Mar 29 19:43:41 2003 EDT Modified files: /phpdoc/en/reference/gettextconfigure.xml Log: Reverting wrong commit by thomas Index: phpdoc/en/reference/gettext/configure.xml diff -u phpdoc/en/reference/gettext/configure.xml:1.2 phpdoc/en/reference/gettext/configure.xml:1.3 --- phpdoc/en/reference/gettext/configure.xml:1.2 Sat Mar 29 19:27:50 2003 +++ phpdoc/en/reference/gettext/configure.xml Sat Mar 29 19:43:41 2003 @@ -1,19 +1,19 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- section id=gettext.installation reftitle.install; para - Para incluir o suporte ao GNU gettext na sua instalação PHP você deve adicionar - a opção option role=configure--with-gettext[=DIR]/option onde DIR é o diretório - de instalação do gettext, o diretório padrão é filename/usr/local/filename. + To include GNU gettext support in your PHP build you must add the option + option role=configure--with-gettext[=DIR]/option where DIR is the + gettext install directory, defaults to filename/usr/local/filename. /para note - titleNota para usuários do Win32/title + titleNote to Win32 Users/title simpara - Para habilitar este módulo no seu ambiente Windows, você deve copiar - a DLL emphasisgnu_gettext.dll/emphasis do diretório DLL do seu pacote - binário PHP/Win32 para a pasta SYSTEM32 do windows. (Ex: C:\WINNT\SYSTEM32 ou - C:\WINDOWS\SYSTEM32). Nas versõs superiores ao PHP 4.2.3 o nome do arquivo mudou para + In order to enable this module on a Windows environment, you must copy + emphasisgnu_gettext.dll/emphasis from the DLL folder of the PHP/Win32 binary + package to the SYSTEM32 folder of your windows machine. (Ex: C:\WINNT\SYSTEM32 + or C:\WINDOWS\SYSTEM32). Starting with PHP 4.2.3 the name changed to emphasislibintl-1.dll/emphasis /simpara /note -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] about users notes
I found a error in a users notes. There is a example missing a /. How can I fix it? I have a cvs account, can I do this or I must do a bug report? Thanks Fernando Correa da Conceição(fernandoc) -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] New example for bzip2
I make a exemple for bzip2, it takes a file compressed and decompress
it, like bzip2 -d does.
Here the code:
?php
$filebz = c:\\file.tar.bz2; //your bzip2 file
$filename = 'c:\\file.tar'; //name to save your file
$bz = bzopen($arquivo, r);
if (!$fp = fopen($filename, 'wb')) {
print Error opening file ($filename);
exit;
}
while($t=bzread($bz)) {
if (!fwrite($fp,$t)) {
print Error writing to file ($filename);
exit;
}
}
bzclose($bz);
fclose($fp);
?
Can I add this example to documentation on bzip2?
The path/filename must be on Linux format?
Thanks
Fernando Correa da Conceição
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Problem with the revcheck page
The same to pt_BR Fernando Martin Samesch escreveu: Hi, http://www.php.net/manual/de/revcheck.html.gz tells me that The de language code is not valid. Is it broken? Martin -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] See also in uniqid.xml
I recommend a See Also in /reference/misc/functions/uniqid.xml to md5() and rand() Thanks Fernando Correa da Conceição -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] /features/file-upload.xml
This is more important than last. There is a mailing list in portuguese, and begin a question about how to make the exemple in file-upload.xml work, and none that uses windows can do, so I began translation of this file and I too can´t use the example. I discover why, I must set upload_tmp_dir to some dir, without this, appear that php don´t know where put the file on upload. The $_FILES['userfile']['name'] has the correct value, but $_FILES['userfile']['tmp_name'] is empty. I don´t have nothing on TMPDIR in my autoexec.bat. This is for PHP 4.2.3, on windows millenium. If someone more can test this and add a note about it. Thanks Fernando Correa da Conceição -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] An error in howto
cvs checkout phpdoc-it-dir This is a example for download the documentetion from cvs in Italian. I don´t know if it´s sure, but this model is not valid for Brazilian Portuguese. cvs checkout phpdoc-pt_BR This is without any dir File cvs.xml, in html result is cvs-checkout.html Fernando Correa da Conceição(fernandoc) -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] phpdoc-pt_BR-dir
What you said is wrong. phpdoc-pt_BR with -dir doesn´t have the howto, the original english files, the ./configure and all other files need to make the manual, none tool to make the revcheck. It have only the translated files, but with it you have to use cvs to download the en files and every another tool. I recommend to use without -dir. It´s more easy to use. Fernando Correa da Conceição(fernandoc) -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] /reference/misc/sleep.xml missing function
In others, all functions is marked with function/function The sleep function delays program execution for the given number of parameterseconds/parameter. In this, why not? Fernando Correa da Conceição(fernandoc) -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
