<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general">
    <title>gmane.comp.php.phptal.general</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1835"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1834"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1833"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1832"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1831"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1830"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1829"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1828"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1827"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1826"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1825"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1824"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1823"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1822"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1821"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1820"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1819"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1818"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1817"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.phptal.general/1816"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1835">
    <title>Re: Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1835</link>
    <description>&lt;pre&gt;On Wed, 16 May 2012 17:04:07 +0100, Thomas Tanghus &amp;lt;thomas-hcAcQX/JTd/R7s880joybQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;  
wrote:


Use:

$translation['foo'] = 'Text ${var}'

or

$translation['foo'] = "Text \${var}"

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-05-17T12:10:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1834">
    <title>Re: Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1834</link>
    <description>&lt;pre&gt;

And then answer was so obvious that I didn't consider it:

&amp;lt;tal:block i18n:name="maxFilesize" tal:content="uploadMaxHumanFilesize" /&amp;gt;
&amp;lt;div i18n:attributes="title" title="titleTranslationKey"&amp;gt;
&amp;lt;/div&amp;gt;

Dang, I have done it so many times. 2 minutes after I push "Send" I figure it 
out :-P

Thanks for the help.

&lt;/pre&gt;</description>
    <dc:creator>Thomas Tanghus</dc:creator>
    <dc:date>2012-05-16T16:14:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1833">
    <title>Re: Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1833</link>
    <description>&lt;pre&gt;
Thanks for the suggestion. That - almost - works. One problem though.

 - We use PHP arrays for translations (don't ask me why), so using the ${var} 
notation gives undefined variable errors. I can hack around that by using 
{var} instead and use a modified PHPTAL_TranslationService::translate() 
method. Grabbed from DummyTranslator in the test dir ;-)

function translate($key, $escape=true) {
    $translations = $this-&amp;gt;getTranslations();
        if (array_key_exists($key, $translations)) {
            $v = $translations[$key];
        } else {
            $v = $key;
        }

        if ($escape) $v = htmlspecialchars($v);

        while (preg_match('/\{(.*?)\}/sm', $v, $m)) {
            list($src, $var) = $m;
            if (!isset($this-&amp;gt;vars[$var])) return "!*$var* is not defined!";
            $v = str_replace($src, $this-&amp;gt;vars[$var], $v);
        }
return $v;
}

and a PHPTAL_TranslationService::setVar method like this:

    public function setVar($key, $value) {
        $this-&amp;gt;vars[$key] = $val&lt;/pre&gt;</description>
    <dc:creator>Thomas Tanghus</dc:creator>
    <dc:date>2012-05-16T16:04:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1832">
    <title>Re: Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1832</link>
    <description>&lt;pre&gt;Maybe I've missed something but my interpretation of your problem is that you want to add variable content into a translation string for an attribute.

How about something like:

&amp;lt;div i18n:attributes="title" title="titleTranslationKey"&amp;gt;
&amp;lt;tal:block i18n:name="maxFilesize" tal:content="uploadMaxHumanFilesize" /&amp;gt;
&amp;lt;/div&amp;gt;

with a po file (assuming you are using gettext) of:

msgid "titleTranslationKey"
msgstr "Drop photo to upload (max ${maxFilesize} MB)"

I am assuming here that the i18n:name key/value pairs are available for attribute translation in the same way they would be for content translation but I haven't seen why that wouldn't be the case.

Robert
----
Robert Goldsmith
rgoldsmith-ekKPKLigxzH10XsdtD+oqA&amp;lt; at &amp;gt;public.gmane.org




On 16 May 2012, at 12:46, Thomas Tanghus wrote:

&lt;/pre&gt;</description>
    <dc:creator>Robert Goldsmith</dc:creator>
    <dc:date>2012-05-16T12:23:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1831">
    <title>Re: Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1831</link>
    <description>&lt;pre&gt;
I found a way around this, in case anybody is interested. It's kind of a hack though.

I assign an instance of my PHPTAL_TranslationService subclass to the template, which lets me do this:

&amp;lt;div tal:define="tooltip php:i18n-&amp;gt;translate('Drop photo to upload') . ' (max ' . uploadMaxHumanFilesize . ')'" 
tal:attributes="title tooltip"&amp;gt;&amp;lt;/div&amp;gt;

It would be nice to be able to do it more elegantly though.

&lt;/pre&gt;</description>
    <dc:creator>Thomas Tanghus</dc:creator>
    <dc:date>2012-05-16T11:46:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1830">
    <title>Variables in i18n:attributes</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1830</link>
    <description>&lt;pre&gt;Hi

I started playing around with phptal this week because I wanted to see if it 
was possible to use as a templating system in ownCloud ( http://owncloud.org 
).
It turned out to be very easy to integrate, and I've only stumbled over one 
problem, and that doesn't have anything to do with the integration.

I have a div where I wan't to translate the title dialog which contains a 
variable assign from my template class with PHPTAL::set().

Using the code below shows ${uploadMaxHumanFilesize} as text.

 &amp;lt;div i18n:attributes="title" title="Drop photo to upload (max 
${uploadMaxHumanFilesize} MB)"&amp;gt;&amp;lt;/div&amp;gt;

Using:

 &amp;lt;div i18n:name="humansize" i18n:attributes="title" title="Drop photo to 
upload (max ${humansize} MB)"&amp;gt;${uploadMaxHumanFilesize}&amp;lt;/div&amp;gt;

Gives the error "Unable to find variable 'humansize' in current scope in 
/path/to/template"

as does:

 &amp;lt;div i18n:name="humansize" i18n:attributes="title string:photo to upload (max 
${humansize} MB)"&amp;gt;${uploadMaxHumanFilesize}&amp;lt;/div&amp;gt;

What is actually worse is that si&lt;/pre&gt;</description>
    <dc:creator>Thomas Tanghus</dc:creator>
    <dc:date>2012-05-12T09:53:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1829">
    <title>Re: Bug when popping context</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1829</link>
    <description>&lt;pre&gt;


IMHO :
- separate slot contexts and var contexts seems (for me, but I just skimmed
through the code) risky : I'm afraid it generates other problems.

- metal:fill-slot is somehow incompatible with any other attributes (but, if you
did the modification, that's you encountered the case)

Therefore, if this was my code, I'd rather implement the following behaviour :
Treat automatically
  &amp;lt;tag metal:fill-slot [other_attrs]&amp;gt;
as
  &amp;lt;tal:block metal:fill-slot&amp;gt;&amp;lt;tag [other_attrs]&amp;gt;

It can be done via a prefilter (some sort of "built-in" prefilter); or maybe
just changing the priority of fill-slot could be sufficient.
&lt;/pre&gt;</description>
    <dc:creator>Pierre-Olivier Vares</dc:creator>
    <dc:date>2012-05-11T12:47:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1828">
    <title>Re: Bug when popping context</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1828</link>
    <description>&lt;pre&gt;On Wed, 09 May 2012 13:32:28 +0100, Pierre-Olivier Vares  
&amp;lt;pov-rrf8xsUWrlzt41TpSn4ztw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


Yeah, it's a tricky piece of code. I've been going back and forth on this  
for a while.

I wonder whether stack of contexts for macros should be handled separately  
(pushSlotContext() rather than pushContext())...

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-05-09T19:54:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1827">
    <title>Bug when popping context</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1827</link>
    <description>&lt;pre&gt;I got the following recursive structure :

&amp;lt;ul&amp;gt;
  &amp;lt;li metal:use-macro="menu_item"&amp;gt;
    &amp;lt;tal:block metal:fill-slot="texte"&amp;gt;File&amp;lt;/tal:block&amp;gt;
    &amp;lt;tal:block metal:fill-slot="sous-menu"&amp;gt;
      &amp;lt;ul&amp;gt;
        &amp;lt;li metal:use-macro="menu_item" tal:define="buggy string:"&amp;gt;
          &amp;lt;tal:block metal:fill-slot="texte"&amp;gt;Open&amp;lt;/tal:block&amp;gt;
&amp;lt;/li&amp;gt;
      &amp;lt;/ul&amp;gt;
    &amp;lt;/tal:block&amp;gt;
  &amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

&amp;lt;tal:block metal:define-macro="menu_item"&amp;gt;
  &amp;lt;li class="menu_item"&amp;gt;
    &amp;lt;a href="#"&amp;gt;&amp;lt;tal:block metal:define-slot="texte" /&amp;gt;&amp;lt;/a&amp;gt;
    &amp;lt;tal:block metal:define-slot="sous-menu" /&amp;gt;
  &amp;lt;/li&amp;gt;
&amp;lt;/tal:block&amp;gt;

Instead of
* File
  * Open

the result is :
* Open
  * Open

If I drop the tal:define="buggy string:", that works.
This behaviour is caused by Context::fillSlot, line 215 :

if ($this-&amp;gt;_parentContext) {
  // setting slots in any context (probably violates TAL, but works around bug
with tal:define popping context after fillslot)
  $this-&amp;gt;_parentContext-&amp;gt;fillSlot($key, $content);
}

As I read the comment, the aim of this code piece is to allow usin&lt;/pre&gt;</description>
    <dc:creator>Pierre-Olivier Vares</dc:creator>
    <dc:date>2012-05-09T12:32:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1826">
    <title>Re: PHP segfaults due Exception in SaxXmlParser</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1826</link>
    <description>&lt;pre&gt;I know that eAccelerator can't handle try-catch block correctly at least in my experience.
In the other hand, PHPTAL uses its special exception handler if exception is finally
passed to outside. They might relate each other on modern PHP, I guess...

How would below(ugly code) work?

// setup $template here

try {
    echo $template-&amp;gt;execute();
    $__dummy = 1;  // Avoiding eAccelerator's bug. 
}
catch(Exception $e) {
    $exception = $e;
}
if(isset($exception)) {
    // echo and exit or...
    $handler = new PHPTAL_ExceptionHandler($template-&amp;gt;getEncoding());
    $handler-&amp;gt;_defaultExceptionHandler($exception);
}


On 2012/05/01, at 23:09, Daniel Jakob wrote:


&lt;/pre&gt;</description>
    <dc:creator>Hisateru Tanaka</dc:creator>
    <dc:date>2012-05-01T15:45:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1825">
    <title>Re: PHP segfaults due Exception in SaxXmlParser</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1825</link>
    <description>&lt;pre&gt;
You're right for versions prior to 1.2.2. But in the current version, it
really leads to a crash of the child process. The crash shows up in the
apache error log.

[Tue May 01 10:05:06 2012] [notice] child pid 24285 exit signal
Segmentation fault (11)
[Tue May 01 10:24:32 2012] [notice] child pid 24252 exit signal
Segmentation fault (11)


&lt;/pre&gt;</description>
    <dc:creator>Daniel Jakob</dc:creator>
    <dc:date>2012-05-01T14:09:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1824">
    <title>Re: PHP segfaults due Exception in SaxXmlParser</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1824</link>
    <description>&lt;pre&gt;I highly doubt that apache is seg-faulting. If you are getting a 500 that could just mean that your error reporting is off.
Sent via BlackBerry by AT&amp;amp;T

-----Original Message-----
From: Daniel Jakob &amp;lt;jakob&amp;lt; at &amp;gt;sc-networks.com&amp;gt;
Sender: phptal-bounces&amp;lt; at &amp;gt;lists.motion-twin.com
Date: Tue, 01 May 2012 10:36:48 
To: &amp;lt;phptal&amp;lt; at &amp;gt;lists.motion-twin.com&amp;gt;
Reply-To: Template Attribute Language for PHP &amp;lt;phptal&amp;lt; at &amp;gt;lists.motion-twin.com&amp;gt;
Subject: [PHPTAL] PHP segfaults due Exception in SaxXmlParser

Hi list

After upgrading TAL to 1.2.2, I found a little problem which makes TAL
quite unuseable in scenarios, when you are not able to control the given
xhtml source. Maybe, the problem depends on newer php versions and/or
eaccelerator.

SaxXmlParser::parseString() throws a PHPTAL_ParserException which isn't
catched by the try/catch block which leads directly to an apache
segfault.
The only exception which gets catched is the PHPTAL_TemplateException.
The ParserException subclasses the TemplateException but - however - &lt;/pre&gt;</description>
    <dc:creator>ajcrites-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-01T12:43:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1823">
    <title>PHP segfaults due Exception in SaxXmlParser</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1823</link>
    <description>&lt;pre&gt;Hi list

After upgrading TAL to 1.2.2, I found a little problem which makes TAL
quite unuseable in scenarios, when you are not able to control the given
xhtml source. Maybe, the problem depends on newer php versions and/or
eaccelerator.

SaxXmlParser::parseString() throws a PHPTAL_ParserException which isn't
catched by the try/catch block which leads directly to an apache
segfault.
The only exception which gets catched is the PHPTAL_TemplateException.
The ParserException subclasses the TemplateException but - however - php
doesn't care about it. This happens every time when I access the script
BUT not the first time. Setting forceReparse to true also 'fixes' the
problem so I assume, the problem is somewhere between the phptal cache
files and the exceptions in php. Maybe, the eaccelerator is involved,
too.
What definitely helps is to explicitly catch PHPTAL_ParserException at
the end of the switch-block (like the TemplateException does).

A sample:

test.xhtml:

&amp;lt;html&amp;gt;
&amp;lt;body&amp;gt;
&amp;lt;span style="" style=""&amp;gt;I kill th&lt;/pre&gt;</description>
    <dc:creator>Daniel Jakob</dc:creator>
    <dc:date>2012-05-01T08:36:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1822">
    <title>Re: Custom namespaces</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1822</link>
    <description>&lt;pre&gt;On Mon, 16 Apr 2012 12:09:39 +0100, Robert Goldsmith  
&amp;lt;rgoldsmith-ekKPKLigxzH10XsdtD+oqA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


The singleton isn't most elegant indeed.

I think you can safely execute  
PHPTAL_Dom_Defs::getInstance()-&amp;gt;registerNamespace() at any time before  
PHPTAL class compiles the template.

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-04-16T20:32:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1821">
    <title>Custom namespaces</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1821</link>
    <description>&lt;pre&gt;Hi all,

I'm looking to add a custom namespace to allow me to do some additional processing on a template. As the processing is something I want to do globally and at template compile time the custom namespace seems like a good option and there seems to be some support for this.

I've looked at the way the namespace code works and I believe I need to:

* Create a new class that extends the PHPTAL_Namespace_Builtin class
* In the constructor of this class register my attributes and the namespace prefix etc.
* Replace the builtin method for createAttributeHandler() so I can load my implementation classes from elsewhere.

This all looks pretty reasonable but now I'm looking at how these namespace classes are initiated and I'm looking at class PHPTAL_Dom_Defs. The comments in this class suggest I can create a subclass and use it to register additional namespaces but then the class is setup as a singleton and I can't see how I'd be able to replace it.

Assuming that all I need to do is call PHPTAL_Dom_Defs's regi&lt;/pre&gt;</description>
    <dc:creator>Robert Goldsmith</dc:creator>
    <dc:date>2012-04-16T11:09:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1820">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1820</link>
    <description>&lt;pre&gt;My personal and big Thank to everyone! Very useful thing done here for all
of us.

Regards,
Anton

On Thursday, April 12, 2012, Kornel Lesiński wrote:



&lt;/pre&gt;</description>
    <dc:creator>Anton Andriyevskyy</dc:creator>
    <dc:date>2012-04-12T21:21:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1819">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1819</link>
    <description>&lt;pre&gt;On Wed, 11 Apr 2012 23:56:08 +0100, Marco Pivetta &amp;lt;ocramius-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;  
wrote:


Added.

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-04-12T15:11:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1818">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1818</link>
    <description>&lt;pre&gt;Registration on packagist is still up to kornel as he has access to the
administration for the repository. Or at least he should setup the callback
Marco Pivetta

http://twitter.com/Ocramius

http://marco-pivetta.com



On 11 April 2012 15:05, Hisateru Tanaka &amp;lt;tanakahisateru-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

_______________________________________________
PHPTAL mailing list
PHPTAL-CzyLcWPZiU5MT9OEwdum/5owlv4uC7bZ&amp;lt; at &amp;gt;public.gmane.org
http://lists.motion-twin.com/mailman/listinfo/phptal
&lt;/pre&gt;</description>
    <dc:creator>Marco Pivetta</dc:creator>
    <dc:date>2012-04-11T22:56:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1817">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1817</link>
    <description>&lt;pre&gt;On Wed, 11 Apr 2012 14:05:14 +0100, Hisateru Tanaka  
&amp;lt;tanakahisateru-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


Done: http://packagist.org/packages/phptal/phptal

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-04-11T22:45:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1816">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1816</link>
    <description>&lt;pre&gt;I was surprised but happier than that.

Can I merge that pull request? If it's so, who should register to Packagist?


On 2012/04/11, at 20:03, Kornel Lesiński wrote:


&lt;/pre&gt;</description>
    <dc:creator>Hisateru Tanaka</dc:creator>
    <dc:date>2012-04-11T13:05:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.phptal.general/1815">
    <title>Re: How about Composer?</title>
    <link>http://permalink.gmane.org/gmane.comp.php.phptal.general/1815</link>
    <description>&lt;pre&gt;On Tue, 10 Apr 2012 23:49:34 +0100, Hisateru Tanaka  
&amp;lt;tanakahisateru-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


Thanks guys. I've added you as collaborators on GitHub.

&lt;/pre&gt;</description>
    <dc:creator>Kornel Lesiński</dc:creator>
    <dc:date>2012-04-11T11:03:08</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.php.phptal.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.php.phptal.general</link>
  </textinput>
</rdf:RDF>

