perldoc2-developers

[perldoc2-developers] additional table 'source'?

[Gregor G. <7go...@in...>]

Hi list,

I think it is essential that translators see the paragraph they
translate (using the web front-end) :-)

I don't see how any code might provide this since there's currently no
connection between the source document and its translations.

We suggest we create a new table 'source document' and add a row
'source' to the table 'document' referring to it.

I don't think we stated this somewhere: A translated paragraph has the
same id as the original paragraph in order to be able to generate the
translated POD easily (see other mail I sent just a few minutes ago).

  Gregor

Re: [perldoc2-developers] additional table 'source'?

[Joergen W. L. <joe...@gm...>]

Gregor Goldbach schrieb:
> Hi list,
> 
> I think it is essential that translators see the paragraph they
> translate (using the web front-end) :-)

Sure - think "split-screen".

1. top    "screen": english original of paragraph
2. bottom "screen": translation

> I don't see how any code might provide this since there's currently no
> connection between the source document and its translations.

True. Not yet. As soon as we have the (most recent) .po file in the DB 
whe can add "views" to it via Catalyst.

> We suggest we create a new table 'source document' and add a row
> 'source' to the table 'document' referring to it.

Why not storing the source in the document table directly?

> I don't think we stated this somewhere: A translated paragraph has the
> same id as the original paragraph in order to be able to generate the
> translated POD easily (see other mail I sent just a few minutes ago).

plus status information.

Joergen

Re: [perldoc2-developers] additional table 'source'?

[Gregor G. <7go...@in...>]

Joergen W. Lang schrieb:

>> I think it is essential that translators see the paragraph they
>> translate (using the web front-end) :-)
> 
> Sure - think "split-screen".
> 
> 1. top    "screen": english original of paragraph
> 2. bottom "screen": translation
> 
>> I don't see how any code might provide this since there's currently no
>> connection between the source document and its translations.
> 
> True. Not yet. As soon as we have the (most recent) .po file in the DB 
> whe can add "views" to it via Catalyst.

So Catalyst accesses both the database and the file system? Hm... I'd
rather see this in the database as well...

>> We suggest we create a new table 'source document' and add a row
>> 'source' to the table 'document' referring to it.
> 
> Why not storing the source in the document table directly?

It's just a feeling that one ought to be able to distinguish source
documents and translations thereof.

  Gregor

Re: [perldoc2-developers] additional table 'source'?

[Gregor G. <7go...@in...>]

Joergen W. Lang schrieb:

>>>> I don't see how any code might provide this since there's currently no
>>>> connection between the source document and its translations.
> 
>>> True. Not yet. As soon as we have the (most recent) .po file in the
>>> DB whe can add "views" to it via Catalyst.
>>
>> So Catalyst accesses both the database and the file system? Hm... I'd
>> rather see this in the database as well...
> 
> Sorry - I don't quite understand. What do you mean by file system? Are
> you referring to the SVN directories?

Yes. I assume with 'view' above you refer to the Model-View-Controller
abstraction in Catalyst.

The current model of the web application I have in mind is that we have
.po files and importer and exporter code to connect the (local) database
to the (remote) subversion repository.

I don't see where a Catalyst 'view' could help there. But, alas! I don't
know Catalyst very much ;)

  Gregor

Re: [perldoc2-developers] additional table 'source'?

[Joergen W. L. <joe...@gm...>]

Gregor Goldbach schrieb:
> Joergen W. Lang schrieb:
> 
>>>>> I don't see how any code might provide this since there's currently no
>>>>> connection between the source document and its translations.

>>>> True. Not yet. As soon as we have the (most recent) .po file in the
>>>> DB whe can add "views" to it via Catalyst.

>>> So Catalyst accesses both the database and the file system? Hm... I'd
>>> rather see this in the database as well...

>> Sorry - I don't quite understand. What do you mean by file system? Are
>> you referring to the SVN directories?
> 
> Yes. I assume with 'view' above you refer to the Model-View-Controller
> abstraction in Catalyst.

and so I did. but...

> The current model of the web application I have in mind is that we have
> .po files and importer and exporter code to connect the (local) database
> to the (remote) subversion repository.

correct.

> I don't see where a Catalyst 'view' could help there. But, alas! I don't
> know Catalyst very much ;)

The Cat view shows/does whatever with the version of the pot which is 
stored in the DB. It does not connect to the SVN repository.


Clear now?

Joergen

P.S.: #perldoc2 @ irc.perl.org is up and running...