Re: A question about local/experimental branches

[Juan Manuel Macías]

Hi, Bastien,

Bastien Guerry writes:

> Ihor Radchenko  writes:
>
>> AFAIU, Juan does not have write access to savannah.
>> Should we give it? Of course, if he is willing to use savannah. Any
>> other public repo is also fine.
>
> Juan, let me know if you need access:
> https://orgmode.org/worg/org-contribute.html#devs

Thank you! I think for the moment I will use GitLab to publish my
experimental branch, if it is not essential to do it in savannah (I am
more used to gitlab). As soon as I publish it, I'll share the
link.

Best regards,

Juan Manuel 

Re: A question about local/experimental branches

[Bastien Guerry]

Ihor Radchenko  writes:

> AFAIU, Juan does not have write access to savannah.
> Should we give it? Of course, if he is willing to use savannah. Any
> other public repo is also fine.

Juan, let me know if you need access:
https://orgmode.org/worg/org-contribute.html#devs

Thanks!

-- 
 Bastien Guerry

Re: A question about local/experimental branches

[Ihor Radchenko]

Bastien Guerry  writes:

> Ihor Radchenko  writes:
>
>> I am not sure if experimental branches can go directly to our savannah,
>> like what Emacs does.
>> Bastien, WDYT?
>
> We did that in the past with Org repo, I see no reason for not doing
> it again with the current Git repo on Savannah: feel free to push
> experimental branches.

AFAIU, Juan does not have write access to savannah.
Should we give it? Of course, if he is willing to use savannah. Any
other public repo is also fine.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: A question about local/experimental branches

[Bastien Guerry]

Ihor Radchenko  writes:

> I am not sure if experimental branches can go directly to our savannah,
> like what Emacs does.
> Bastien, WDYT?

We did that in the past with Org repo, I see no reason for not doing
it again with the current Git repo on Savannah: feel free to push
experimental branches.

-- 
 Bastien Guerry

Re: A question about local/experimental branches

[Juan Manuel Macías]

Ihor Radchenko writes:

> P.S. Juan, I will need some time to review previous discussions on
> inline special blocks before I can comment on your work in depth.

No problem, Ihor. These days I had enough free time to develop my idea,
translate it into code and get something usable from which it could be
discussed. As I mentioned, the export to HTML and LaTeX is complete and
works fine, but I'll probably stop there for a long time. I mean, I
won't go any further and I will dedicate myself to continuing testing
the code already written and fixing possible bugs. Partly because I
don't have enough knowledge of odt to work on this backend, which would
be the next step.

Thanks for the info!

-- 
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño 
editorial y ortotipografía

Re: A question about local/experimental branches

[Ihor Radchenko]

Juan Manuel Macías  writes:

> I've noticed that the code for my implementation of the new
> 'inline-special-block' experimental element is growing. In addition, I
> introduce modifications and improvements daily. So I think it might be a
> good idea to make my local branch public, in case someone wants to try
> it or contribute to the project.
>
> My question is if there is any set of good practices to do this, or is
> it enough to publish the local branch 'as is'.

See https://orgmode.org/worg/org-contribute.html#orgfd0d3cb
You can just share the link to your branch.

I am not sure if experimental branches can go directly to our savannah,
like what Emacs does.
Bastien, WDYT?

P.S. Juan, I will need some time to review previous discussions on
inline special blocks before I can comment on your work in depth.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

A question about local/experimental branches

[Juan Manuel Macías]

Hi,

I've noticed that the code for my implementation of the new
'inline-special-block' experimental element is growing. In addition, I
introduce modifications and improvements daily. So I think it might be a
good idea to make my local branch public, in case someone wants to try
it or contribute to the project.

My question is if there is any set of good practices to do this, or is
it enough to publish the local branch 'as is'.

Currently I have completed, and are perfectly usable, the export to
LaTeX and HTML. I have also improved the syntax. Now, if aliases are
used for group optional attributes, it is not necessary to put :alias
foo, but @foo@. Example:

  #+options: inline-special-block-aliases:(("latin" :lang "la" :color blue 
:prelatex "\\itshape " :html "style=\"font-style:italic;\""))

  This is an example of Latin text: &_[@latin@]{lorem ipsum dolor sit amet}.

  This is an example of Latin text with small caps: &_[@latin@ :smallcaps 
t]{lorem ipsum dolor sit amet}.

LaTeX ==>

  This is an example of Latin text: 
{\color{blue}\foreignlanguage{latin}{\itshape lorem ipsum dolor sit amet}}.

  This is an example of Latin text with small caps: 
{\scshape{}\color{blue}\foreignlanguage{latin}{\itshape lorem ipsum dolor sit 
amet}}

HTML ==>

  This is an example of Latin text: lorem ipsum dolor sit amet.

  This is an example of Latin text with small caps: lorem 
ipsum dolor sit amet.


Related: https://list.orgmode.org/87ttlyloyr@posteo.net/

Best regards,

Juan Manuel

-- 
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño 
editorial y ortotipografía

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com