This is a good point. I would counter with my opinion that the
templates are just as necessary to begin installation, but the point is
still valid.
The question becomes can the current translation process be easily
extended to handling the SQL files separate from the parser? That would
probably
Translating SQL has a high likelihood of inducing unrecoverable error.
The translation parser already just *barely* works as it is for
HTML::Template::Pro files. I wouldn't trust it, or extending a custom
tangle of code like it to handle a totally different language in files that
are necessary to
Would it be possible to have the current translation process include the
SQL files. Then it's just a matter of having the .po files parsed prior
to packaging a release, and have the SQL files for other languages
created that way.
There would probably need to be a user defined function in the data
Hi Ricardo and all,
At 13.11 29/07/2009, Ricardo Dias Marques wrote:
>I think there should be only:
>- 1 (ONE) Unimarc Bibliographic SQL file
>- and 1 (ONE) Unimarc Authorites SQL file
>
>... and NOT one of those for EACH language. The current situation,
>IMHO, leads to much Copy + Paste work, whe
