Now that 1.9.0 is out, I'm moving all news prior to 1.9.0 to oldnews.phtml which is a new static page that fully supports translation. There's more to do before it's ready for a commit but it should be all done at the weekend. I'm also building the ideas about simplifying the site into the next version but structural changes like this aren't well suited to incremental commits so I need to wait until each bit is working.
Question: Do we want the newest news translated?
The choice, so far, is:
1. Keep a simple text format and translate when it's time to move it to
oldnews (by converting to php).
2. Create a new news format where news files are actually PHP. This involves
something like:
<?php
echo _("<b>Accouncement</b> ...");
echo _("translatable content");
?>
(the announcement and time would need to be separate to make it simple to
display those in a banner.)
3. Or simply edit the index.phtml page when adding new news - inserting the
new text as PHP (to translate) or HTML (to not), and commit to svn.
I think it's probably more work than it's worth but it's relatively simple to
spot syntax errors as PHP is very noisy over such things. Others?
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpDHK2vyVLl2.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
