Am 07/26/2014 11:33 PM, schrieb Kay Schenk:
On 07/26/2014 02:59 AM, Marcus (OOo) wrote:
Am 07/26/2014 12:51 AM, schrieb Emanuele:
Marcus (OOo) wrote:
please have a look. The links 2, 3 and 4 do not display correctly:
http://ooo-site.staging.apache.org/projects/native-lang.html
Most likely is because of the bits of html present (the<div
class="Acta1"> and corresponding closing div wrapping the text), judging
from the fact that only the links inside this block are not processed.
I've created a new test page as MDTEXT. Looks good now. Thanks for the
hint:
http://ooo-site.staging.apache.org/projects/native-lang-new.html
Any special need to create this as MDTEXT? Otherwise I would suggest
to turn it back into HTML.
The reason I converted the text to md is because I find the table much
easier to handle in md rather than in html (actually it's still a bit
confusing, I should have added some spacing to align things better), but
up to you. ;)
Tables in HTML can be indeed a bit nasty. ;-)
@Kay:
I've started a new table to show separate status in different parts of
the webpages.
I can think of that the overall status can be different to the initial
homepage and download status. I've created also a column for the
download as IMHO this is the most important part for our software and
deserves an own status. If you (or others) think different the table can
consists of only 2 columns for overall status and homepage.
Example:
Finnish:
The initial homepage is OK but not localized.
The download is OK and most recent but not localized.
Therefore the overall status in "unmaintained".
Yes, big work to get an initial status for all languages and parts. But
could be worth to get an overview and every new interested volunteer can
see with one view what's up.
Does this help? Should we expand it to all languages?
Differentiating between the website status and the distribution status
is definitely a good move. I know this isn't exactly what you showed but
maybe we can think along that line. What if we If we just showed
"website status" and "distribution status"?
it seems for you "distribution" is more than the pure download. What
exactly? We should write this down in a sentence to make it clear.
And, to make things more simple, just list the websites as either
"maintained" or "not maintained". What specific aspect of this is
important of course, but if volunteers are interested in helping, I'm
sure they would just check out the sites themselves to see what might be
done.
Right, it should be kept simple.
We might want to include a small definition and just say that a website
status of "not maintained" could mean a variety of issues but primarily
the fact that the website home page or downlaod page has not been
localized for the language, or that the download information is
presenting the correct information.
I think you are also right here.
Example:
Language Website Status Distribution Status
======== ============== ===================
Afar(aa) not maintained none existent
German (de) maintained most recent
Finnish not maintained most recent
If we went this way, I think it would be easier to maintain the
native-lang page and be less confusing for volunteers to interpret the
status.
You convinced me. ;-)
Do you want to go on in ".../native-lang-new.mdtext"? When finished and
all agreed we can move it to ".../native-lang.mdtext".
So, there's my much more than .02! :}
The long table is more expensive than just 2 ct. :-P
Good night for today.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
