Laurent Blume wrote:
The strings end up in a Java properties file, but unfortunately
there's no simple answer to your question because the strings are
output by different methods, some of which preserve quotes and some
of which require them to be doubled. Sorry I can't be more specific
than that. Perhaps using the HTML escape (') might be more
predictable, but I'd have to check that out before recommending it.
I'm sure it's not easy, some kind of solution must be found though, else
it can lead to corrupt web pages.
As a generalisation it is error and warning messages that get the
double-quotes stripped as they pass through Java's MessageFormat class,
but some others do as well. It's a pain, I'll see if I can think of a
solution. It might also help a little if the CTI tool gave the labels
as well as the text. You can see the current versions of the master and
translated files in the Auth repo - see
http://src.opensolaris.org/source/xref/website/oso/auth/AuthWebapp/src/configuration/
Also, I think that keeping HTML code in the translation strings is a
mistake, but of course, I don't know what lead to that choice, There
might be no better option.
We've only done so where there is a link that forms part of a sentence -
different languages will put it in different positions, so it has to be
part of the text.
Back to something you wrote in your previous email:
Some recently-modified text is awaiting translation, we will update
the application with the new translations as soon as we have them
available, and new translations are welcome.
How do we know which text has been modified and should be retranslated?
CTI still says 100% is done.
We need to give an updated 'master' file to the CTI folks, so the new
strings haven't yet appeared in the CTI tool yet.
And now for some untranslated strings that should/could be:
- the "Set Language" string
- the footer with website TOU, etc (but maybe that depends on fully
moving to the new site?)
- the privacy text there:
https://auth.opensolaris.org/register.action?lang=fr
- "Information and offers" there:
https://auth.opensolaris.org/edit.action
- The types of collectives there:
https://auth.opensolaris.org/collectives.action
- The type of agreement there:
https://auth.opensolaris.org/agreements.action
Yes, all of those are new, as I mentioned above.
- Also, there's an option to deactivate the account, but not to delete
it. This is legally required in many countries (Facebook is having
trouble with that lack of compliance). It should be added. Unless
deactivate really means delete? It doesn't sound like it though.
We can delete accounts, but we've had cases where people have closed
their account by accident and then subsequently wanted it reopened. The
plan is therefore to allow people to inactivate their accounts, then
delete them entirely after a set period. The only data we retain on
deletion is the username, so we can stop people re-registering as a
deleted account and masquerading as the 'deleted' person. Of course we
can also delete accounts immediately if people really want that, and
understand that they'd have to re-register under a new username if they
wanted to rejoin.
--
Alan Burlison
--
_______________________________________________
website-discuss mailing list
[email protected]
