Quoting Michael Wiedmann <mw(a)miwie.in-berlin.de&gt;: What about po4a-whatever -o "translate=secondary" -o "translate=tertiary" -o "indent=bridgehead" blabla ? It should do the trick, even if it's not completely tested yet. Just give it a try, please. Yuh, not. Actually, the XML handling is rather "experimental", yet. I'd like to make a real parser and so one there, but I'm not sure how to do that. Yet. For now, I'm sorry, but my hard disk crashed friday, so I'm doomed to webmail for now. Please forgive me for the delay, I'll be right back. Mt.

* martin.quinson(a)free.fr <martin.quinson(a)free.fr&gt; wrote [040627 07:49]: ... If I use the the following syntax (according to the man-page the options should be a space separated list of extra tags!), it works: po4a-whatever -o "translate=secondary tertiary bridgehead" ... Michael -- mw(a)miwie.in-berlin.de http://www.miwie.org

* Martin Quinson <martin.quinson(a)free.fr&gt; wrote [040630 23:59]: This was just a mistake on my side - or at least I was reading too fast over the documentation and was not sure how to pass extra options to the modules. I think the documentation on this issue is good enough. Michael -- mw(a)miwie.in-berlin.de http://www.miwie.org

On Sun, Jun 27, 2004 at 07:49:33AM +0200, martin.quinson(a)free.fr wrote: Ok, I'm back. How should I support it? Is it reasonnable to do the same trick than for CDATA (which is not implemented yet either)? Can I just ignore this tag, and present it to the user as a string to translate, or is there any cleaver action? Thanks for your help, I am veeeery bad in xml. Mt. -- Ouvrir une école, c'est fermer une prison. -- Victor Hugo

Quoting Michael Wiedmann <mw(a)miwie.in-berlin.de&gt;: The point is that the current design of the Sgml module makes it very difficult to simply ignore some parts of the document because I use an external parser. I can change them into text before launching the parser, and then turn they back to their values. That's the trick I use to protect the entities, for example. &version; is rewritten to PO4A-ampversion; before launching nsgml, and then back while generating the document/po files. But if I do so, I'm afraid that nsgml begins whining about CDATA being placed where it shouldn't. I am near the point where I decide that nsgml creates more problem than it solves. Making a ?ML parser in perl from the scratch shouldn't be that difficult after all. The only reasons why I don't go further and reimplement my own parser is the complexity of the code. As I said recently, I don't even remember the differences between translate and indent (I guess that's a good argument to reingeenering the code ;). And there is some weird parts to support sgml specificities such as conditional compilation (ok, that would be also easier without nsgml). There is the file inclusion mecanism, also (but it should be generalized, and put in the core of po4a so that other module can use it). Ok, the real reason is my chronical lack of time, and the fear of introducing new bugs which I would have to fix ASAP since some people begin to use po4a... I'm gonna try masking the <?bla?> as well as CDATA to nsgml, to see if it does the trick. Mt.

On Fri, Jul 16, 2004 at 10:21:46AM +0200, Jordi Vilalta wrote: It's maybe time that: - you create a user on alioth, so that we can give you the cvs write access - you show us the code of this xml module ? Yes, the more urgent is to move out the file inclusion mecanism to TransTractor.pm I may try to work on this next week, but I'm completely overhelmed currently. If you want to work on this, please mail the list before so that we make sure we don't dupplicate the effort, and please process. The problem is that detecting a file inclusion in the source is format dependant. In sgml, that's done with entities while the macro so is used in groff. A solution may be to do something like that at the begining of each module: map { if (/^.so (.*)/) $doc->includefile($1) } $doc->{TT}{doc_in}; It is a very crude proof of concept, though. The right solution may even be completely different ;) For the encoding issues, it's even worse. I don't have even the begining of an answer. We may have to wait until Denis comes back. Well. I hope so, but if I break po4a, it's kind of my responsability to fix it, isn't it? -- Testing can only prove the presence of bugs. --- Dijkstra

On Fri, Jul 16, 2004 at 11:15:35PM +0200, Jordi Vilalta wrote: done. You should have the commit rights. Try not to abuse it ;) Why that? Just commit your working version in the CVS without changing the Chooser documentation neither the MANIFEST. That way, it will be available from the CVS, but not from distributed versions. That's what cvs is made for ;) [about file inclusion] hehe, if you want to know to truth, I kind of expected it, but map is such a cool contruct that I wanted to bring your attention to it... Yes, you are right. If I get ride of this nasty nsgml, I could implement this include_file() the same way that unshiftline(). It would include the file at the current begin of the document. The process would then to parse the document with calls to shiftline, and when you find a file inclusion request, you do an include_file, and then continue with your shiftline()s. That's clean. I like that. I just have to get ride of sgml. But I can't do so without threating my professional occupations. I /really/ don't have the time. Even if I would prefer to do it ;) Please. Bye, Mt. -- C'est dégueulasse, y'a pas une meuf. C'est pas un temps à faire du surf ! -- Les malpolis

martin.quinson(a)free.fr wrote: None so far. Michael --