Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-03-23 Thread Zoom.Quiet 
On Thu, Mar 22, 2018 at 10:51 PM, Edward K. Ream  wrote:
>
>
> On Sat, Feb 17, 2018 at 9:14 AM, Zoom.Quiet  wrote:
>>
>> 2 years ago: Re: How to collaborate using Leo
>> https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ
>> discuss about  Leonard(Leo user) and Nancy(not Leo user) how to work
>> together,
>> the result is :
>> @clean be upgraded, and support perfect auto merge from Nancy fixed
>> resource files.
>>
>> but for the doc. translate project:
>> work in doc/LeoDocs.leo is the necessarily, because:
>>
>> 0: the target for translate doc. of Leo , just for Chinese Nancy start
>> love Leo
>> 1: so contributor base LeoDocs.leo is the only right start
>
>
> I think the best solution may be to put everything in an @clean or (if Nancy
> agrees) an @file node.  That way updates happen automatically, which
> doesn't/can't happen with the actual .leo files.
>

Sayeahooo..
in the begin , i think same with u,
but when u try, there is so many rST special append commend,
such as:

@rst docs/leoLinks.html

...

.. _`Icons`:icons.html

...

@ @rst-options
call_docutils=False
stylesheet_path=..\doc
write_intermediate_file = True
@c

will all need reformat as normal format,
that will make bigger diff with official .leo documentation,

if official LeoDoc.leo upgrade,
translation usage LeoDoc_zh.leo can not easy know what is changed.

so, i think the better way for LeoDoc,
is Official LeoDoc.leo also make all @rst ->@clean

change Doc. is only .leo @rST ->.rst,
update as .leo @clean <-> .rst
so work with .leo or .rst , is all ok.

right?


> Edward
>

-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-03-22 Thread Edward K. Ream 
On Sat, Feb 17, 2018 at 9:14 AM, Zoom.Quiet  wrote:

> 2 years ago: Re: How to collaborate using Leo
> https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ
> discuss about  Leonard(Leo user) and Nancy(not Leo user) how to work
> together,
> the result is :
> @clean be upgraded, and support perfect auto merge from Nancy fixed
> resource files.
>
> but for the doc. translate project:
> work in doc/LeoDocs.leo is the necessarily, because:
>
> 0: the target for translate doc. of Leo , just for Chinese Nancy start
> love Leo
> 1: so contributor base LeoDocs.leo is the only right start
>

​I think the best solution may be to put everything in an @clean or (if
Nancy agrees) an @file node.  That way updates happen automatically, which
doesn't/can't happen with the actual .leo files.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-02-20 Thread Zoom.Quiet 
On Tue, Feb 20, 2018 at 12:45 AM, Edward K. Ream  wrote:
> On Mon, Feb 19, 2018 at 9:33 AM, Zoom.Quiet  wrote:
>> after test, i confirm:
>>
>> - change @rst -> @clean, will lost so many rST need support by Leo
>> - and @rst really can not auto merge changed from out files
>
>
> Yes, this is a problem. I don't know of any simple solution.
>

for my experience, the old version of Leo base Tangle & Untangle make
3 worlds exchange:
0: product world -> out files
1: think world -> outlines
2: work world -> edit pane

but Leo support more and more commands (like @others <>...)
that make the one action pair Tangle & Untangle can not simple support
all kinds of commands expand actions,
so EKR build new file type commands (like @rst @clean), include
special Tangle processes;
but product world -> think world, is more complex...?

but @clean can base 'Recovered Nodes' auto merged product world change,
why others file type nodes can not?

in face, git/hg/cvs/... all kinds of VCS can:
0: auto fix most conflict
1: if not, will export good structural diff log

so for Leo reflect these info. just 2 ways:
0: perfect understand conflict/diff, and re-write right node content
1: not re-write any node, just insert nodes report the conflict/diff,
help people result them

i hope Leo support the simple way:
just insert alert nodes near conflict contents,
and lock the save action, until fixed all alert nodes ; -)

> I would consider writing scripts that would read/write parts of LeoDocs.leo
>
> to some external file.  It would even be possible to execute these scripts
> automatically using, say, Leo's 'save2' and 'open2' events.  See this page.
>
http://leoeditor.com/writingPlugins.html#summary-of-event-handlers

WoW ... Leo support s many events now, that look like some thing
in the deep base is maybe not lite enough?

> Edward
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.



-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-02-19 Thread Edward K. Ream 
On Mon, Feb 19, 2018 at 9:33 AM, Zoom.Quiet  wrote:

>
> after test, i confirm:
>
> - change @rst -> @clean, will lost so many rST need support by Leo
>


> - and @rst really can not auto merge changed from out files
>

​Yes, this is a problem. I don't know of any simple solution.

I would consider writing scripts that would read/write parts of LeoDocs.leo​

​to some external file​.  It would even be possible to execute these
scripts automatically using, say, Leo's 'save2' and 'open2' events.  See this
page .

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-02-19 Thread Zoom.Quiet 
On Sat, Feb 17, 2018 at 11:14 PM, Zoom.Quiet  wrote:
> 2 years ago: Re: How to collaborate using Leo
> https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ
> discuss about  Leonard(Leo user) and Nancy(not Leo user) how to work together,
> the result is :
> @clean be upgraded, and support perfect auto merge from Nancy fixed
> resource files.
>
> but for the doc. translate project:
> work in doc/LeoDocs.leo is the necessarily, because:
>
> 0: the target for translate doc. of Leo , just for Chinese Nancy start love 
> Leo
> 1: so contributor base LeoDocs.leo is the only right start
>
> BUT collaborate in github, there is always 2 ways:
> 0: like svn, usage github as one kinds of collaborate Repo., member
> with Repo. ACL;
> 1: base DVCS , usage Fork->Pull-Request flow;
>
> in the doc. translate project, the contributor in different level,
> will produce different result:
> 0: member of Repo. with write ACL, can push LeoDocs.leo, and usage
> Rst3 export new translate results;
> 1: contributor from fork Repo., if P-R  LeoDocs.leo, the member can
> not decide accept or not base diff from .leo, because mix so many XML
> info.
>
> SO my question is :
> how to make different roles in doc. translate project all in effective
> edit action?
>
> in my mind:
> 0: member of Project, work in self .leo such as LeoDocs_ZQ.leo, push
> new .rst and .leo into Repo., because we all Leonard
> 1: contributor from fork Repo., work with .rst files,P-R only include
> .rst diff info., because can not requirement  Nancy immediately became
> Leonard
>
> BUT there is some problems:
> 0: members .leo can not auto merge by git? or How to auto merge others
> member's new translated into self .leo?
> 1: new translate work result if merge succeed by git from
> Pull-Request, how to make Member's .leo accept them?
>
> for now , i only think out one way:
> - change the nodes in doc/LeoDocs.leo @rst --> @clean
> - so whatever Nancy/Leonard's translate result will auto exchange with .rst
> - in the same time, every member can keep self outlines in .leo
>

after test, i confirm:

- change @rst -> @clean, will lost so many rST need support by Leo
- and @rst really can not auto merge changed from out files

and, if base same .leo collaborate, member's contributor will make
Merge conflict by git:

Traceback (most recent call last):
  File "/opt/bin/Leo-5.4/leo/core/leoFileCommands.py", line 1251,
in parse_leo_file
parser.parse(theFile) # expat does not support parseString
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/sax/expatreader.py",
line 110, in parse
xmlreader.IncrementalParser.parse(self, source)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/sax/xmlreader.py",
line 123, in parse
self.feed(buffer)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/sax/expatreader.py",
line 217, in feed
self._err_handler.fatalError(exc)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/sax/handler.py",
line 38, in fatalError
raise exception
SAXParseException: :2288:1: not well-formed (invalid token)
read outline in 0.08 seconds


so what is the effective collaborate with .leo for translate LeoDocs ?


> and is there better collaborate ways for doc. translate project?
>
>
> On Thu, Feb 1, 2018 at 10:28 PM, OMlalala  wrote:
>> Overview
>>
>> Hi, I use Leo from one month ago, very enjoy ;-)
>> and I want to make chinese version Doc for spread the perfect Leo, any
>> advices?
>>
> ...
>
> leo-editor-cn
> https://github.com/DebugUself/leo-editor-cn
>
>
> --
> life is pathetic, go Pythonic! 人生苦短, Python当歌!
> 俺: http://zoomquiet.io
> 授: http://creativecommons.org/licenses/by-sa/2.5/cn/
> 怒: 冗余不做,日子甭过!备份不做,十恶不赦!
> KM keep growing environment culture which promoting organization learning!



-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2018-02-17 Thread Zoom.Quiet 
2 years ago: Re: How to collaborate using Leo
https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ
discuss about  Leonard(Leo user) and Nancy(not Leo user) how to work together,
the result is :
@clean be upgraded, and support perfect auto merge from Nancy fixed
resource files.

but for the doc. translate project:
work in doc/LeoDocs.leo is the necessarily, because:

0: the target for translate doc. of Leo , just for Chinese Nancy start love Leo
1: so contributor base LeoDocs.leo is the only right start

BUT collaborate in github, there is always 2 ways:
0: like svn, usage github as one kinds of collaborate Repo., member
with Repo. ACL;
1: base DVCS , usage Fork->Pull-Request flow;

in the doc. translate project, the contributor in different level,
will produce different result:
0: member of Repo. with write ACL, can push LeoDocs.leo, and usage
Rst3 export new translate results;
1: contributor from fork Repo., if P-R  LeoDocs.leo, the member can
not decide accept or not base diff from .leo, because mix so many XML
info.

SO my question is :
how to make different roles in doc. translate project all in effective
edit action?

in my mind:
0: member of Project, work in self .leo such as LeoDocs_ZQ.leo, push
new .rst and .leo into Repo., because we all Leonard
1: contributor from fork Repo., work with .rst files,P-R only include
.rst diff info., because can not requirement  Nancy immediately became
Leonard

BUT there is some problems:
0: members .leo can not auto merge by git? or How to auto merge others
member's new translated into self .leo?
1: new translate work result if merge succeed by git from
Pull-Request, how to make Member's .leo accept them?

for now , i only think out one way:
- change the nodes in doc/LeoDocs.leo @rst --> @clean
- so whatever Nancy/Leonard's translate result will auto exchange with .rst
- in the same time, every member can keep self outlines in .leo

and is there better collaborate ways for doc. translate project?


On Thu, Feb 1, 2018 at 10:28 PM, OMlalala  wrote:
> Overview
>
> Hi, I use Leo from one month ago, very enjoy ;-)
> and I want to make chinese version Doc for spread the perfect Leo, any
> advices?
>
...

leo-editor-cn
https://github.com/DebugUself/leo-editor-cn


-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.