subject:"Re\: native\-lang.html suggestions now in staging..."


Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):

Am 07/28/2014 07:07 PM, schrieb Kay Schenk:



On 07/28/2014 01:05 AM, Tal Daniel wrote:

On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com wrote:




On 07/26/2014 10:16 PM, Tal Daniel wrote:

Don't you think this page should exist elsewhere, not on the site?
maybe

on

openoffice.apache.org native language section? It's feels as a status
page, rather than a page for visitors.

Tal


I think it's just where it is for historical purposes, and I see your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download due to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?



Nonactive/non-maintained websites will, eventually, be removed from the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)


yes...


choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.


Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html


Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say, e.g.,
outdated + maintained. This means that the content is old but there is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.


the discussion about formatting is all fine and all good. But without 
content is doesn't matter, right? ;-)


Please can we first finalize the content. Then we can beautifying the 
webpage step by step.


Thanks

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-30 Thread Kay Schenk

On 07/30/2014 11:05 AM, Marcus (OOo) wrote:
Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):
Am 07/28/2014 07:07 PM, schrieb Kay Schenk:

On 07/28/2014 01:05 AM, Tal Daniel wrote:
On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:

On 07/26/2014 10:16 PM, Tal Daniel wrote:
Don't you think this page should exist elsewhere, not on the site?
maybe
on
openoffice.apache.org native language section? It's feels as a
status
page, rather than a page for visitors.

Tal

I think it's just where it is for historical purposes, and I see your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download due to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?

Nonactive/non-maintained websites will, eventually, be removed from the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)

yes...

choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.

Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html

Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say, e.g.,
outdated + maintained. This means that the content is old but there is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.

the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus

That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

so it should be easy for others to make further changes.

As usual, older versions can be had from svn --

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/projects/native-lang.mdtext?view=log

I'm not sure how long it takes for the latest revision to show up in
this list.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-30 Thread Alexandro Colorado

On 7/30/14, Kay Schenk kay.sch...@gmail.com wrote:

On 07/30/2014 11:05 AM, Marcus (OOo) wrote:
Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):
Am 07/28/2014 07:07 PM, schrieb Kay Schenk:

On 07/28/2014 01:05 AM, Tal Daniel wrote:
On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:

Tal

I think it's just where it is for historical purposes, and I see your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my
simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download due
to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?

Nonactive/non-maintained websites will, eventually, be removed from
the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)

yes...

choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.

Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.

the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus

That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

Not sure how that is necesarry thats why we have a staging site. I
would publish the current mdtext, and then see the next changes on
staging.

so it should be easy for others to make further changes.

As usual, older versions can be had from svn --

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/projects/native-lang.mdtext?view=log

I'm not sure how long it takes for the latest revision to show up in
this list.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-30 Thread Kay Schenk

On 07/30/2014 12:02 PM, Alexandro Colorado wrote:
On 7/30/14, Kay Schenk kay.sch...@gmail.com wrote:

On 07/30/2014 11:05 AM, Marcus (OOo) wrote:
Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):
Am 07/28/2014 07:07 PM, schrieb Kay Schenk:

On 07/28/2014 01:05 AM, Tal Daniel wrote:
On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:

Tal

I think it's just where it is for historical purposes, and I see your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my
simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download due
to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?

Nonactive/non-maintained websites will, eventually, be removed from
the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)

yes...

choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.

Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.

the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus

That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

Not sure how that is necesarry thats why we have a staging site. I
would publish the current mdtext, and then see the next changes on
staging.

Maybe a bit of an explanation. I published the mdtext but it gets
converted to html on publication. The mdtext had been in stating for a
few days. This is still only a working document since it is not the
one being linked, and I thought for non-committers, this way might be
easier. Maybe I'm wrong about that.

so it should be easy for others to make further changes.

As usual, older versions can be had from svn --

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/projects/native-lang.mdtext?view=log

I'm not sure how long it takes for the latest revision to show up in
this list.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-30 Thread Alexandro Colorado

On 7/30/14, Kay Schenk kay.sch...@gmail.com wrote:

On 07/30/2014 12:02 PM, Alexandro Colorado wrote:
On 7/30/14, Kay Schenk kay.sch...@gmail.com wrote:

On 07/30/2014 11:05 AM, Marcus (OOo) wrote:
Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):
Am 07/28/2014 07:07 PM, schrieb Kay Schenk:

On 07/28/2014 01:05 AM, Tal Daniel wrote:
On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:

Tal

I think it's just where it is for historical purposes, and I see
your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my
simpler
definitions. See the definition for maintained. The download
links
from these pages work, but some are NOT to a localized download due
to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?

Nonactive/non-maintained websites will, eventually, be removed from
the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)

yes...

choosing the language from the drop-down-box is a fast and cheap way
to
come to unmaintained webpages that have the large hint (we have to
make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.

Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html

Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say,
e.g.,
outdated + maintained. This means that the content is old but there
is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.

the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus

That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

Not sure how that is necesarry thats why we have a staging site. I
would publish the current mdtext, and then see the next changes on
staging.

I am mostly on a KISS (Keep it simple stupid) creating '-new'
documents are mostly a bad idea since is not surprise we have a lot of
'*-new' documents somewhat polluting the site tree.

Non-commiters can always post their version on their hosts (I try to
use people.apache.org) but there is always space on google drive, or
github to put your version with your tweaks, maybe is a good test case
to move to GIT and work with branches. I suggest checking out gitflow
for a good workflow system when dealing with git commiters.

so it should be easy for others to make further changes.

As usual, older versions can be had from svn --

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/projects/native-lang.mdtext?view=log

I'm not sure how long it takes for the latest revision to show up in
this list.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
-
MzK

To be trusted is a greater compliment than being loved.
-- George MacDonald

-
To unsubscribe, e-mail:

Re: native-lang.html suggestions now in staging...


Am 07/30/2014 09:57 PM, schrieb Alexandro Colorado:

On 7/30/14, Kay Schenkkay.sch...@gmail.com  wrote:



On 07/30/2014 12:02 PM, Alexandro Colorado wrote:

On 7/30/14, Kay Schenkkay.sch...@gmail.com  wrote:



On 07/30/2014 11:05 AM, Marcus (OOo) wrote:

Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):

Am 07/28/2014 07:07 PM, schrieb Kay Schenk:



On 07/28/2014 01:05 AM, Tal Daniel wrote:

On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:




On 07/26/2014 10:16 PM, Tal Daniel wrote:

Don't you think this page should exist elsewhere, not on the site?
maybe

on

openoffice.apache.org  native language section? It's feels as a
status
page, rather than a page for visitors.

Tal


I think it's just where it is for historical purposes, and I see
your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my
simpler
definitions. See the definition for maintained. The download
links
from these pages work, but some are NOT to a localized download due
to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?



Nonactive/non-maintained websites will, eventually, be removed from
the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)


yes...


choosing the language from the drop-down-box is a fast and cheap way
to
come to unmaintained webpages that have the large hint (we have to
make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.


Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html


Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say,
e.g.,
outdated + maintained. This means that the content is old but there
is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.


the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus


That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html


Not sure how that is necesarry thats why we have a staging site. I
would publish the current mdtext, and then see the next changes on
staging.


Maybe a bit of an explanation. I published the mdtext but it gets
converted to html on publication. The mdtext had been in stating for a
few days. This is still only a working document since it is not the
one being linked, and I thought for non-committers, this way might be
easier. Maybe I'm wrong about that.


I am mostly on a KISS (Keep it simple stupid) creating '-new'
documents are mostly a bad idea since is not surprise we have a lot of
'*-new' documents somewhat polluting the site tree.


no problem, they can be deleted.


Non-commiters can always post their version on their hosts (I try to
use people.apache.org) but there is always space on google drive, or
github to put your version with your tweaks, maybe is a good test case
to move to GIT and work with branches. I suggest checking out gitflow
for a good workflow system when dealing with git commiters.


This would *maybe* solve a problem we don't have now. ;-)

Sorry, but this dicussion lead to nowhere.

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...


Am 07/30/2014 08:51 PM, schrieb Kay Schenk:



On 07/30/2014 11:05 AM, Marcus (OOo) wrote:

Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):

Am 07/28/2014 07:07 PM, schrieb Kay Schenk:



On 07/28/2014 01:05 AM, Tal Daniel wrote:

On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:




On 07/26/2014 10:16 PM, Tal Daniel wrote:

Don't you think this page should exist elsewhere, not on the site?
maybe

on

openoffice.apache.org  native language section? It's feels as a
status
page, rather than a page for visitors.

Tal


I think it's just where it is for historical purposes, and I see your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download due to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?



Nonactive/non-maintained websites will, eventually, be removed from the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)


yes...


choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.


Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html


Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say, e.g.,
outdated + maintained. This means that the content is old but there is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.


the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus


That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

so it should be easy for others to make further changes.


thats not what I wanted. IMHO we haven't finished our discussion about 
status (and maybe further content).


Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-30 Thread Kay Schenk



On 07/30/2014 01:44 PM, Marcus (OOo) wrote:
 Am 07/30/2014 08:51 PM, schrieb Kay Schenk:


 On 07/30/2014 11:05 AM, Marcus (OOo) wrote:
 Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):
 Am 07/28/2014 07:07 PM, schrieb Kay Schenk:


 On 07/28/2014 01:05 AM, Tal Daniel wrote:
 On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
 wrote:



 On 07/26/2014 10:16 PM, Tal Daniel wrote:
 Don't you think this page should exist elsewhere, not on the site?
 maybe
 on
 openoffice.apache.org  native language section? It's feels as a
 status
 page, rather than a page for visitors.

 Tal

 I think it's just where it is for historical purposes, and I see
 your
 point. We can move it.

 Anyway, my new version is at:

 http://ooo-site.staging.apache.org/projects/native-lang-new.html

 Even after I suggested it, I'm not sure I'm 100% happy with my
 simpler
 definitions. See the definition for maintained. The download links
 from these pages work, but some are NOT to a localized download
 due to
 editing (by me some weeks ago) to at least get them to some correct
 download area. :/ So, what to do with these gray areas?


 Nonactive/non-maintained websites will, eventually, be removed
 from the
 language selection box;a call for volunteers is also appropriate, in
 order
 to revive such a website (another column?)

 yes...

 choosing the language from the drop-down-box is a fast and cheap way to
 come to unmaintained webpages that have the large hint (we have to make
 this sure) to help to get it complete again.

 So, I think it would not be good to delete it from the selection.

 Ok, I just changed the definitions slightly and corrected some errors
 I'd made in assessment yesterday as well. This needs another pair of
 eyes!

 again, at:
 http://ooo-site.staging.apache.org/projects/native-lang-new.html

 Maybe we should take the content (current or outdated) and the work on
 it (maintained or help wanted) into account? With this we can say,
 e.g.,
 outdated + maintained. This means that the content is old but
 there is
 someone who is working on updates.

 Here my further idea:

 current The website is OK and needs no help.

 outdated The website has old content and needs to be updated.

 maintained Someone is already actively working on the website.

 help wanted Volunteers are welcome to help updating the website.

 the discussion about formatting is all fine and all good. But without
 content is doesn't matter, right? ;-)

 Please can we first finalize the content. Then we can beautifying the
 webpage step by step.

 Thanks

 Marcus

 That would be nice! :)

 I just put the page with the changes I made recently into production at:

 http://www.openoffice.org/projects/native-lang-new.html

 so it should be easy for others to make further changes.
 
 thats not what I wanted. IMHO we haven't finished our discussion about
 status (and maybe further content).
 
 Marcus

Well I will not be the least bit upset if you revert this change.


 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 

-- 
-
MzK

To be trusted is a greater compliment than being loved.
   -- George MacDonald

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...


Am 07/30/2014 10:50 PM, schrieb Kay Schenk:



On 07/30/2014 01:44 PM, Marcus (OOo) wrote:

Am 07/30/2014 08:51 PM, schrieb Kay Schenk:



On 07/30/2014 11:05 AM, Marcus (OOo) wrote:

Am 07/28/2014 09:43 PM, schrieb Marcus (OOo):

Am 07/28/2014 07:07 PM, schrieb Kay Schenk:



On 07/28/2014 01:05 AM, Tal Daniel wrote:

On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenkkay.sch...@gmail.com
wrote:




On 07/26/2014 10:16 PM, Tal Daniel wrote:

Don't you think this page should exist elsewhere, not on the site?
maybe

on

openoffice.apache.org   native language section? It's feels as a
status
page, rather than a page for visitors.

Tal


I think it's just where it is for historical purposes, and I see
your
point. We can move it.

Anyway, my new version is at:

http://ooo-site.staging.apache.org/projects/native-lang-new.html

Even after I suggested it, I'm not sure I'm 100% happy with my
simpler
definitions. See the definition for maintained. The download links
from these pages work, but some are NOT to a localized download
due to
editing (by me some weeks ago) to at least get them to some correct
download area. :/ So, what to do with these gray areas?



Nonactive/non-maintained websites will, eventually, be removed
from the
language selection box;a call for volunteers is also appropriate, in
order
to revive such a website (another column?)


yes...


choosing the language from the drop-down-box is a fast and cheap way to
come to unmaintained webpages that have the large hint (we have to make
this sure) to help to get it complete again.

So, I think it would not be good to delete it from the selection.


Ok, I just changed the definitions slightly and corrected some errors
I'd made in assessment yesterday as well. This needs another pair of
eyes!

again, at:
http://ooo-site.staging.apache.org/projects/native-lang-new.html


Maybe we should take the content (current or outdated) and the work on
it (maintained or help wanted) into account? With this we can say,
e.g.,
outdated + maintained. This means that the content is old but
there is
someone who is working on updates.

Here my further idea:

current The website is OK and needs no help.

outdated The website has old content and needs to be updated.

maintained Someone is already actively working on the website.

help wanted Volunteers are welcome to help updating the website.


the discussion about formatting is all fine and all good. But without
content is doesn't matter, right? ;-)

Please can we first finalize the content. Then we can beautifying the
webpage step by step.

Thanks

Marcus


That would be nice! :)

I just put the page with the changes I made recently into production at:

http://www.openoffice.org/projects/native-lang-new.html

so it should be easy for others to make further changes.


thats not what I wanted. IMHO we haven't finished our discussion about
status (and maybe further content).

Marcus


Well I will not be the least bit upset if you revert this change.


ahm no ;-) What I meant is, we were in the discussion of the status, I 
made a further suggestion (see above: current, outdated, maintained and 
help wanted) and then it turnd into how to style the text.


I just want to get the discussion back to the topic as IMHO we have not 
an agreed text.


Marcus



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

On 7/28/14, Kay Schenk kay.sch...@gmail.com wrote:


 On 07/28/2014 02:19 PM, Marcus (OOo) wrote:
 Am 07/28/2014 11:05 PM, schrieb Alexandro Colorado:
 Here is a sample of a sortable table (click on the header you want to
 sort).
 http://people.apache.org/~jza/table.html

 the table will get long. So, to have it sortable is a nice advantage.

 yes...this is a nice feature. We have to see what happens since the page
 is mdtext now.


 The glyphicons are not set yet, hopefully later.

 Some icons could help. However, to show simply a green and red color
 (maybe also yellow) should do the same trick.

 Marcus

 Since our web pages are now under ALv2, I'm not sure if we can include
 Creative Commons licensed objects in them. See --

 http://www.apache.org/foundation/license-faq.html#GPL

 We'd need to ask legal.

 Coloring the cells is certainly a simple way to go assuming it doesn't
 make things too busy.

I used fontawesome.io instead which is under a OFL - SIL. However if
we are going to use bootstrap (applied to the theme) we should be
aware that glyphicons are included in the framework and are the
default.
http://people.apache.org/~jza/table.html

If you want to choose another iconset for the current/outdated, you
can make your pick from the iconset here:
http://fontawesome.io/icons/








 On 7/28/14, Alexandro Coloradoj...@oooes.org  wrote:
 On 7/26/14, Marcus (OOo)marcus.m...@wtnet.de  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 (thediv
 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?

 As a design concern I will preffer using images than labels. It makes
 the user identify better the nature. Alternatively we could use
 Glyphicons usually can make somewhat of a cleaner code, and also are
 more smaller than a pixel-base image. Also frameworks like Bootstrap
 already include them on the framework.
 http://glyphicons.com/
 http://glyphicons.bootstrapcheatsheets.com/

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org


 --
 -
 MzK

 To be trusted is a greater compliment than being loved.
-- George MacDonald

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org




-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

Kay Schenk wrote:

 On 07/28/2014 02:19 PM, Marcus (OOo) wrote:
 Am 07/28/2014 11:05 PM, schrieb Alexandro Colorado:
 Here is a sample of a sortable table (click on the header you want to
 sort).
 http://people.apache.org/~jza/table.html
 the table will get long. So, to have it sortable is a nice advantage.
 yes...this is a nice feature. We have to see what happens since the page
 is mdtext now.

 The glyphicons are not set yet, hopefully later.
 Some icons could help. However, to show simply a green and red color
 (maybe also yellow) should do the same trick.

 Marcus
 Since our web pages are now under ALv2, I'm not sure if we can include
 Creative Commons licensed objects in them. See --

 http://www.apache.org/foundation/license-faq.html#GPL

 We'd need to ask legal.

 Coloring the cells is certainly a simple way to go assuming it doesn't
 make things too busy.



http://glyphicons.com/license/

So, the free version is distributed under CC BY 3.0:
https://issues.apache.org/jira/browse/LEGAL-96
so apparently still open, *but*:

 GLYPHICONS Halflings are also a part of Bootstrap from Twitter, and
they are released under the same license as Bootstrap.

that means: MIT, which falls under category A according to
https://www.apache.org/legal/resolved.html#category-a

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-29 Thread Kay Schenk

On Tue, Jul 29, 2014 at 8:32 AM, Alexandro Colorado j...@oooes.org wrote:

 On 7/28/14, Kay Schenk kay.sch...@gmail.com wrote:
 
 
  On 07/28/2014 02:19 PM, Marcus (OOo) wrote:
  Am 07/28/2014 11:05 PM, schrieb Alexandro Colorado:
  Here is a sample of a sortable table (click on the header you want to
  sort).
  http://people.apache.org/~jza/table.html
 
  the table will get long. So, to have it sortable is a nice advantage.
 
  yes...this is a nice feature. We have to see what happens since the page
  is mdtext now.



I have not discovered a way to incorporate page level styles into a markup
document aside our site-wide css located in css/ooo.css which is the style
definitions for the whole site. If someone else knows any tricks, please
let us know.

 Marcus has a blog article on localization waiting on the finalization of
the revised native-lang page. It would be nice if we could get a new
native-lang page into production soon even if it does not have graphic cues
or the sorting mechanism.



 
  The glyphicons are not set yet, hopefully later.
 
  Some icons could help. However, to show simply a green and red color
  (maybe also yellow) should do the same trick.
 
  Marcus
 
  Since our web pages are now under ALv2, I'm not sure if we can include
  Creative Commons licensed objects in them. See --
 
  http://www.apache.org/foundation/license-faq.html#GPL
 
  We'd need to ask legal.
 
  Coloring the cells is certainly a simple way to go assuming it doesn't
  make things too busy.

 I used fontawesome.io instead which is under a OFL - SIL. However if
 we are going to use bootstrap (applied to the theme) we should be
 aware that glyphicons are included in the framework and are the
 default.
 http://people.apache.org/~jza/table.html

 If you want to choose another iconset for the current/outdated, you
 can make your pick from the iconset here:
 http://fontawesome.io/icons/

 
 
 
 
 
 
 
  On 7/28/14, Alexandro Coloradoj...@oooes.org  wrote:
  On 7/26/14, Marcus (OOo)marcus.m...@wtnet.de  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 (thediv
  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?
 
  As a design concern I will preffer using images than labels. It makes
  the user identify better the nature. Alternatively we could use
  Glyphicons usually can make somewhat of a cleaner code, and also are
  more smaller than a pixel-base image. Also frameworks like Bootstrap
  already include them on the framework.
  http://glyphicons.com/
  http://glyphicons.bootstrapcheatsheets.com/
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
  For additional commands, e-mail: dev-h...@openoffice.apache.org
 
 
  --
  -
  MzK
 
  To be trusted is a greater compliment than being loved.
 -- George MacDonald
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
  For additional commands, e-mail: dev-h...@openoffice.apache.org
 
 


 --
 Alexandro Colorado
 Apache OpenOffice Contributor
 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: native-lang.html suggestions now in staging...

On 7/29/14, Kay Schenk kay.sch...@gmail.com wrote:
 On Tue, Jul 29, 2014 at 8:32 AM, Alexandro Colorado j...@oooes.org wrote:

 On 7/28/14, Kay Schenk kay.sch...@gmail.com wrote:
 
 
  On 07/28/2014 02:19 PM, Marcus (OOo) wrote:
  Am 07/28/2014 11:05 PM, schrieb Alexandro Colorado:
  Here is a sample of a sortable table (click on the header you want to
  sort).
  http://people.apache.org/~jza/table.html
 
  the table will get long. So, to have it sortable is a nice advantage.
 
  yes...this is a nice feature. We have to see what happens since the
  page
  is mdtext now.



 I have not discovered a way to incorporate page level styles into a markup
 document aside our site-wide css located in css/ooo.css which is the style
 definitions for the whole site. If someone else knows any tricks, please
 let us know.

That's why I was pushing for a way to keep content and style
separated. mdtext is not a good way to store content since you are
already setting a format. The ideal measure was to have this on a json
file (or xml) and let Javascript generate the table (using loops and
stuff). That way it doesnt matter if its a table or a list or an HTML
control.


  Marcus has a blog article on localization waiting on the finalization of
 the revised native-lang page. It would be nice if we could get a new
 native-lang page into production soon even if it does not have graphic cues
 or the sorting mechanism.



 
  The glyphicons are not set yet, hopefully later.
 
  Some icons could help. However, to show simply a green and red
  color
  (maybe also yellow) should do the same trick.
 
  Marcus
 
  Since our web pages are now under ALv2, I'm not sure if we can include
  Creative Commons licensed objects in them. See --
 
  http://www.apache.org/foundation/license-faq.html#GPL
 
  We'd need to ask legal.
 
  Coloring the cells is certainly a simple way to go assuming it doesn't
  make things too busy.

 I used fontawesome.io instead which is under a OFL - SIL. However if
 we are going to use bootstrap (applied to the theme) we should be
 aware that glyphicons are included in the framework and are the
 default.
 http://people.apache.org/~jza/table.html

 If you want to choose another iconset for the current/outdated, you
 can make your pick from the iconset here:
 http://fontawesome.io/icons/

 
 
 
 
 
 
 
  On 7/28/14, Alexandro Coloradoj...@oooes.org  wrote:
  On 7/26/14, Marcus (OOo)marcus.m...@wtnet.de  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 (thediv
  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?
 
  As a design concern I will preffer using images than labels. It
  makes
  the user identify better the nature. Alternatively we could use
  Glyphicons usually can make somewhat of a cleaner code, and also are
  more smaller than a pixel-base image. Also frameworks like Bootstrap
  already include them on the framework.
  http://glyphicons.com/
  http://glyphicons.bootstrapcheatsheets.com/
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
  For additional commands, e-mail: dev-h...@openoffice.apache.org
 
 
  --
  -
  MzK
 
  To be

Re: native-lang.html suggestions now in staging...

Kay Schenk wrote:
 On Tue, Jul 29, 2014 at 8:32 AM, Alexandro Colorado j...@oooes.org wrote:

 On 7/28/14, Kay Schenk kay.sch...@gmail.com wrote:

 On 07/28/2014 02:19 PM, Marcus (OOo) wrote:
 Am 07/28/2014 11:05 PM, schrieb Alexandro Colorado:
 Here is a sample of a sortable table (click on the header you want to
 sort).
 http://people.apache.org/~jza/table.html
 the table will get long. So, to have it sortable is a nice advantage.
 yes...this is a nice feature. We have to see what happens since the page
 is mdtext now.

 I have not discovered a way to incorporate page level styles into a markup
 document aside our site-wide css located in css/ooo.css which is the style
 definitions for the whole site. If someone else knows any tricks, please
 let us know.

Speak in general is kind of difficult, and I may have misunderstood what
you want to achieve, but, speaking general, I can see two ways:
1) (preferred by me) in each mdtext file you should be able to specify
an bodytag that becomes an id on the body tag, with that you don't need
to use any page-specific css file, you can just prefix your styles with
#idofthepage and those will be applied only for that page,
2) (a bit of an extreme solution) create a new path in lib/path.pm for
the specific page/directory/pattern, create a new template for it and
add the necessary files to the header.

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

Alexandro Colorado wrote:
 That's why I was pushing for a way to keep content and style
 separated. mdtext is not a good way to store content since you are
 already setting a format. The ideal measure was to have this on a json
 file (or xml) and let Javascript generate the table (using loops and
 stuff). That way it doesnt matter if its a table or a list or an HTML
 control.

Content has to be associated in a way or another with a structure, and
mdtext gives exactly the general structure the text should have.
Then CSS defines the style.

But the md used by the Apache CMS is extended and supports some more
stuff.
For example, if I understood the problem right, you can do the same
thing with markdown:

 Language  | Website | Distribution
-- | 
[Afar (aa)](/aa/)   | {.fa fa-ban} |   {.fa fa-warning}

etc.

Let me put again a reference to what I think is the extended markdown
the CMS supports:
https://michelf.ca/projects/php-markdown/extra/

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

2014-07-29 Thread Ariel Constenla-Haile

On Tue, Jul 29, 2014 at 10:06:02AM -0700, Kay Schenk wrote:
 I have not discovered a way to incorporate page level styles into a markup
 document aside our site-wide css located in css/ooo.css which is the style
 definitions for the whole site. If someone else knows any tricks, please
 let us know.

I'm not following this thread, so may be I don't get what you are trying
to do. If you want to know how to add a particular CSS to a MarkDown
page, take a look at

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/es/noticias/index.mdtext?view=markup
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/es/noticias/styles.css?view=markup

http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/product/index.mdtext?view=markup
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/product/styles.css?view=markup


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: Digital signature

Re: native-lang.html suggestions now in staging...

On Tue, Jul 29, 2014 at 1:47 PM, Emanuele emanuel...@gmail.com wrote:

 Alexandro Colorado wrote:
  That's why I was pushing for a way to keep content and style
  separated. mdtext is not a good way to store content since you are
  already setting a format. The ideal measure was to have this on a json
  file (or xml) and let Javascript generate the table (using loops and
  stuff). That way it doesnt matter if its a table or a list or an HTML
  control.

 Content has to be associated in a way or another with a structure, and
 mdtext gives exactly the general structure the text should have.
 Then CSS defines the style.


Sure but structure is more with database structure, not with style
structure. For example, maybe you might want to use a dt-dd or ul-li and
generate a tabular data through CSS. 
Something like this: http://blog.andremakram.com/?p=7




 But the md used by the Apache CMS is extended and supports some more
 stuff.
 For example, if I understood the problem right, you can do the same
 thing with markdown:

  Language  | Website | Distribution
 -- | 
 [Afar (aa)](/aa/)   | {.fa fa-ban} |   {.fa fa-warning}

 etc.

 Let me put again a reference to what I think is the extended markdown
 the CMS supports:
 https://michelf.ca/projects/php-markdown/extra/

 Emanuele

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org




-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: native-lang.html suggestions now in staging...

On Tue, Jul 29, 2014 at 1:47 PM, Emanuele emanuel...@gmail.com wrote:

Alexandro Colorado wrote:
That's why I was pushing for a way to keep content and style
separated. mdtext is not a good way to store content since you are
already setting a format. The ideal measure was to have this on a json
file (or xml) and let Javascript generate the table (using loops and
stuff). That way it doesnt matter if its a table or a list or an HTML
control.

Content has to be associated in a way or another with a structure, and
mdtext gives exactly the general structure the text should have.
Then CSS defines the style.

Sure but structure is more with database structure, not with style
structure. For example, maybe you might want to use a dt-dd or ul-li
and generate a tabular data through CSS. This is usually done on
menus when doing some webdev.

Mdtext is not a logical structure but a presentation structure which
basically restrict the development of mantainable websites because it
doesnt allow the modification through CSS or JS.

The structure there should have been something like a JSON string
carrying the values for country, link, state, localization, Javascript
could then parse that data, and put it on some table structure and
loop through it.
Something like this: http://blog.andremakram.com/?p=7

But the md used by the Apache CMS is extended and supports some more
stuff.
For example, if I understood the problem right, you can do the same
thing with markdown:

Language | Website | Distribution
-- |
[Afar (aa)](/aa/) | {.fa fa-ban} | {.fa fa-warning}

etc.

Let me put again a reference to what I think is the extended markdown
the CMS supports:
https://michelf.ca/projects/php-markdown/extra/

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614

On 7/29/14, Alexandro Colorado j...@oooes.org wrote:
On Tue, Jul 29, 2014 at 1:47 PM, Emanuele emanuel...@gmail.com wrote:

Content has to be associated in a way or another with a structure, and
mdtext gives exactly the general structure the text should have.
Then CSS defines the style.

Sure but structure is more with database structure, not with style
structure. For example, maybe you might want to use a dt-dd or ul-li and
generate a tabular data through CSS.
Something like this: http://blog.andremakram.com/?p=7

But the md used by the Apache CMS is extended and supports some more
stuff.
For example, if I understood the problem right, you can do the same
thing with markdown:

Language | Website | Distribution
-- |
[Afar (aa)](/aa/) | {.fa fa-ban} | {.fa fa-warning}

etc.

Let me put again a reference to what I think is the extended markdown
the CMS supports:
https://michelf.ca/projects/php-markdown/extra/

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

--
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

Alexandro Colorado wrote:
 Mdtext is not a logical structure but a presentation structure which
 basically restrict the development of mantainable websites because it
 doesnt allow the modification through CSS or JS.

hmm...
Probably we are looking at the problem from two very different
perspectives.
Markdown allows to define styles and ids in the markup.
It allows to use HTML (provided you don't put markdown inside html
blocks, that's query a limitations at times, but it can be worked
around) so you can add additional styles.
Yes, it doesn't allow to add classes or ids to certain elements (e.g. ul
and tables are the two I know for sure). This could be worked around
using the CMS.

 The structure there should have been something like a JSON string
 carrying the values for country, link, state, localization, Javascript
 could then parse that data, and put it on some table structure and
 loop through it.
 Something like this: http://blog.andremakram.com/?p=7

Sorry, I probably missed a piece of discussion, so I hope you don't mind
a question: why do you want use a JSON strings to build a table that is
already built in HTML or markdown? (Genuine question.)
I mean: I used in the download page example a json-like block, because
the resulting table was an expansion of the block (multiplied by the
number of languages IIRC), but in that case the json string and the
table would be a 1:1 match (i.e. any cell of the table would require a
corresponding entry in the json array), so I can't see exactly the
advantage of one against the other.

Emanuele

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...

On Tue, Jul 29, 2014 at 4:29 PM, Emanuele emanuel...@gmail.com wrote:

 Alexandro Colorado wrote:
  Mdtext is not a logical structure but a presentation structure which
  basically restrict the development of mantainable websites because it
  doesnt allow the modification through CSS or JS.

 hmm...
 Probably we are looking at the problem from two very different
 perspectives.
 Markdown allows to define styles and ids in the markup.
 It allows to use HTML (provided you don't put markdown inside html
 blocks, that's query a limitations at times, but it can be worked
 around) so you can add additional styles.
 Yes, it doesn't allow to add classes or ids to certain elements (e.g. ul
 and tables are the two I know for sure). This could be worked around
 using the CMS.

  The structure there should have been something like a JSON string
  carrying the values for country, link, state, localization, Javascript
  could then parse that data, and put it on some table structure and
  loop through it.
  Something like this:
 
 http://blog.andremakram.com/?p=7
 
 Sorry, I probably missed a piece of discussion, so I hope you don't mind
 a question: why do you want use a JSON strings to build a table that is
 already built in HTML or markdown? (Genuine question.)


JSON or XML is a datatype source, that has no presentation defined. For me
Markdown is same as HTML, it's formated data that can't be moified that
easily (change an HTML table into a list for example). XML, JSON are
datatypes that are builted to be consumed and presented into a different
presentations (take ODF for example, or SVG). 


 I mean: I used in the download page example a json-like block, because
 the resulting table was an expansion of the block (multiplied by the
 number of languages IIRC), but in that case the json string and the
 table would be a 1:1 match (i.e. any cell of the table would require a
 corresponding entry in the json array), so I can't see exactly the
 advantage of one against the other.


Basically take the presentation out of the equation, also making it more
easy to maintain. I gave you an example of how it can play here.
http://andremakram.com/blog/sourcecode/html_table_js_json/

If you ever worked with bash scripts (sed, awk, variable expansions, etc),
having serialized data is much simpler to process like this than with an
HTML file which could be a pain to get the right transformation.




 Emanuele

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org




-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: native-lang.html suggestions now in staging...

2014-07-29 Thread Kay Schenk

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 07/29/2014 11:58 AM, Ariel Constenla-Haile wrote:
 On Tue, Jul 29, 2014 at 10:06:02AM -0700, Kay Schenk wrote:
 I have not discovered a way to incorporate page level styles into a markup
 document aside our site-wide css located in css/ooo.css which is the style
 definitions for the whole site. If someone else knows any tricks, please
 let us know.
 
 I'm not following this thread, so may be I don't get what you are trying
 to do. If you want to know how to add a particular CSS to a MarkDown
 page, take a look at
 
 http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/es/noticias/index.mdtext?view=markup
 http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/es/noticias/styles.css?view=markup
 
 http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/product/index.mdtext?view=markup
 http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/product/styles.css?view=markup
 
 
 Regards
 

Well I have no idea where you found this information -- it's the
styles.css file! -- but thank you! It's not mentioned in the ASF
information concerning the CMS. I suppose if you are much more familiar
with markdown, you would know it, but, alas, I am not.



- -- 
- -
MzK

To be trusted is a greater compliment than being loved.
   -- George MacDonald
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT2DfeAAoJEJ8zlgVF1GcuSTkIAMNL2mgjAPdMbXQIxZ1IOc+V
gMR5AiU1gGj7bbaluC6AFJ1o6aOIM2Kydg+JkdzlbF2NyZrzp9t1WzNJoy5R1gcC
gtmnFsKmhYcyLBSFH67NMkOdLdS4P3UoW/E9gEIZwxKpstKnl9mjZHbQajcHPV4G
tvssYMPveg9l+38gOzGTwvLk7yA6/2DFaaLDpgFT7iXb+QPGJm9Se7gY2OeRPkm3
y1CZkeItNQN+eWWQ4WH7+WwnR+s6eaMupaTNhq8aunSC2rAd22wfgZbH+d3qGZsK
1TZKMlOl0jEHWv2bmkHtX3SoBNpdG+HAfn0LdMG/aX8RsHgRaomKaDF3xS6n/Hk=
=xGIV
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: native-lang.html suggestions now in staging...