Re: [basex-talk] Formatting attributes as an indented list?

2023-03-07 Thread Patrick Durusau

Christian,

Thanks indeed to both you and Gunther Rademacher!

Excellent work!

Patrick

On 2/21/23 06:41, Christian Grün wrote:

Hi Jonathan, hi Patrick,

The new serialization parameter 'indent-attributes' is already available [1]:

(: provided globally :)
declare option output:indent 'yes';
declare option output:indent-attributes 'yes';


(: provided locally :)
serialize(
   ,
   map {
 'indent-attributes': true(),
 'indent': true()
   }
)

Result:


Thank you to Gunther Rademacher, who contributed the code solution!

A new stable snapshot is available [2]. The serialization parameter
may officially be supported with XQuery 4 [3].

Hope this helps,
Christian

[1] https://docs.basex.org/wiki/Serialization
[2] https://files.basex.org/releases/latest/
[3] https://github.com/qt4cg/qtspecs/issues/358#issuecomment-1436595401



On Wed, Feb 15, 2023 at 7:05 PM Jonathan Robie  wrote:

Hi Christian,

I prefer to be able to require one attribute per line.  This is important for 
Git diffs, which are the main reason we care.

Jonathan

On Wed, Feb 15, 2023 at 11:31 AM Christian Grün  
wrote:

Hi Jonathan,

Thanks for sharing your tidy settings.

With the given configuration, all attributes except for the first are
returned in a separate line…



In Patrick’s example, some attributes were returned in a single line
(possibly depending on the expected string length). Maybe it was
generated via Saxon (just a guess):



Do you have a preference which representation would be required, or do
you think the details are not that relevant?

We could possibly add a custom serialization parameter similar to
tidy’s 'indent-attributes' option, and it would probably be easier to
ignore the expected string length.

All the best,
Christian


--
Patrick Durusau
patr...@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau



OpenPGP_signature
Description: OpenPGP digital signature


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-21 Thread Christian Grün
Hi Jonathan, hi Patrick,

The new serialization parameter 'indent-attributes' is already available [1]:

(: provided globally :)
declare option output:indent 'yes';
declare option output:indent-attributes 'yes';


(: provided locally :)
serialize(
  ,
  map {
'indent-attributes': true(),
'indent': true()
  }
)

Result:


Thank you to Gunther Rademacher, who contributed the code solution!

A new stable snapshot is available [2]. The serialization parameter
may officially be supported with XQuery 4 [3].

Hope this helps,
Christian

[1] https://docs.basex.org/wiki/Serialization
[2] https://files.basex.org/releases/latest/
[3] https://github.com/qt4cg/qtspecs/issues/358#issuecomment-1436595401



On Wed, Feb 15, 2023 at 7:05 PM Jonathan Robie  wrote:
>
> Hi Christian,
>
> I prefer to be able to require one attribute per line.  This is important for 
> Git diffs, which are the main reason we care.
>
> Jonathan
>
> On Wed, Feb 15, 2023 at 11:31 AM Christian Grün  
> wrote:
>>
>> Hi Jonathan,
>>
>> Thanks for sharing your tidy settings.
>>
>> With the given configuration, all attributes except for the first are
>> returned in a separate line…
>>
>> > rule="S-IO"
>> cltype="VerbElided">
>>
>> In Patrick’s example, some attributes were returned in a single line
>> (possibly depending on the expected string length). Maybe it was
>> generated via Saxon (just a guess):
>>
>> 
>>
>> Do you have a preference which representation would be required, or do
>> you think the details are not that relevant?
>>
>> We could possibly add a custom serialization parameter similar to
>> tidy’s 'indent-attributes' option, and it would probably be easier to
>> ignore the expected string length.
>>
>> All the best,
>> Christian


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-15 Thread Christian Grün
Hi Jonathan,

I think we can offer you a solution soon. I have created a GitHub issue to
document the progress [1].

All the best,
Christian

[1] https://github.com/BaseXdb/basex/issues/2174



Jonathan Robie  schrieb am Mi., 15. Feb. 2023,
19:05:

> Hi Christian,
>
> I prefer to be able to require one attribute per line.  This is important
> for Git diffs, which are the main reason we care.
>
> Jonathan
>
> On Wed, Feb 15, 2023 at 11:31 AM Christian Grün 
> wrote:
>
>> Hi Jonathan,
>>
>> Thanks for sharing your tidy settings.
>>
>> With the given configuration, all attributes except for the first are
>> returned in a separate line…
>>
>> > rule="S-IO"
>> cltype="VerbElided">
>>
>> In Patrick’s example, some attributes were returned in a single line
>> (possibly depending on the expected string length). Maybe it was
>> generated via Saxon (just a guess):
>>
>> 
>>
>> Do you have a preference which representation would be required, or do
>> you think the details are not that relevant?
>>
>> We could possibly add a custom serialization parameter similar to
>> tidy’s 'indent-attributes' option, and it would probably be easier to
>> ignore the expected string length.
>>
>> All the best,
>> Christian
>>
>


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-15 Thread Jonathan Robie
Hi Christian,

I prefer to be able to require one attribute per line.  This is important
for Git diffs, which are the main reason we care.

Jonathan

On Wed, Feb 15, 2023 at 11:31 AM Christian Grün 
wrote:

> Hi Jonathan,
>
> Thanks for sharing your tidy settings.
>
> With the given configuration, all attributes except for the first are
> returned in a separate line…
>
>  rule="S-IO"
> cltype="VerbElided">
>
> In Patrick’s example, some attributes were returned in a single line
> (possibly depending on the expected string length). Maybe it was
> generated via Saxon (just a guess):
>
> 
>
> Do you have a preference which representation would be required, or do
> you think the details are not that relevant?
>
> We could possibly add a custom serialization parameter similar to
> tidy’s 'indent-attributes' option, and it would probably be easier to
> ignore the expected string length.
>
> All the best,
> Christian
>


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-15 Thread Christian Grün
Hi Jonathan,

Thanks for sharing your tidy settings.

With the given configuration, all attributes except for the first are
returned in a separate line…



In Patrick’s example, some attributes were returned in a single line
(possibly depending on the expected string length). Maybe it was
generated via Saxon (just a guess):



Do you have a preference which representation would be required, or do
you think the details are not that relevant?

We could possibly add a custom serialization parameter similar to
tidy’s 'indent-attributes' option, and it would probably be easier to
ignore the expected string length.

All the best,
Christian


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-15 Thread Jonathan Robie
Hi Christian,

Currently, I am using HTML tidy to reformat the XML output.  It gives me
the formatting I need, which is Git-diff friendly.

Jonathan


$ nodes % tidy --version

HTML Tidy for Apple macOS version 5.6.0

$ nodes % tidy -config tidy.config  03-luke.xml

Sample Output:












wrote:

> Hi Patrick
>
> I noticed that the attributes for the wg element had not been aligned, so
> I was wondering if you were thinking of a more advanced rule.
>
> Or would you possibly like to supply the names of the elements for which
> the alignment should take place?
>
> Best,
> Christian
>
>
>
> Patrick Durusau  schrieb am Mi., 15. Feb. 2023,
> 03:51:
>
>> Christian,
>>
>> Ah, no, it isn't a length of element name + attribute but the ability to
>> align attributes for an element as you see in my post for the > element. Each key/value is followed by a line return.
>>
>> In the mean time, the current version of tidy has been added to the
>> workflow to produce the desired results.
>>
>> But it would be great to have it native to BaseX!
>>
>> Thanks!
>>
>> Patrick
>>
>> On 2/14/23 01:30, Christian Grün wrote:
>> > Hi Patrick,
>> >
>> > There’s currently no serialization parameter to control the custom
>> > indentation of attributes.
>> >
>> > If I get you correctly, you’d like to get attributes indented if the
>> > string length of the element name and the attributes exceed a specific
>> > maximum length?
>> >
>> > Best,
>> > Christian
>> >
>> >
>> > On Mon, Feb 13, 2023 at 9:10 PM Patrick Durusau 
>> wrote:
>> >> Greetings!
>> >>
>> >> I've been tasked with using BaseX to produce:
>> >>
>> >> *
>> >>
>> >>
>> >>   
>> >>  > rule="Np-Appos">
>> >> > >>after=" "
>> >>class="noun"
>> >>gbiType="proper"
>> >>xml:id="n57001001001"
>> >>lemma="Παῦλος"
>> >>normalized="Παῦλος"
>> >>strong="3972"
>> >>number="singular"
>> >>gender="masculine"
>> >>case="nominative"
>> >>gloss="Paul"
>> >>domain="093001"
>> >>ln="93.294a"
>> >>morph="N-NSM"
>> >>unicode="Παῦλος">Παῦλος
>> >>
>> >> *
>> >>
>> >> The indenting is easy enough and I can even make it deeper if required
>> >> but is there a command for serialization that will properly format the
>> >> attributes?
>> >>
>> >> My personal suspicion is that inserting \n when each attribute is
>> >> serialized (and not on the last one) is the easier route but I promised
>> >> to investigate the command line.
>> >>
>> >> Have I overlooked something in the very fine manual?
>> >>
>> >> Hope everyone is having a great week!
>> >>
>> >> Patrick
>> >>
>> >> --
>> >> Patrick Durusau
>> >> patr...@durusau.net
>> >> Technical Advisory Board, OASIS (TAB)
>> >> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> >> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>> >>
>> >> Another Word For It (blog): http://tm.durusau.net
>> >> Homepage: http://www.durusau.net
>> >> Twitter: patrickDurusau
>> >>
>> --
>> Patrick Durusau
>> patr...@durusau.net
>> Technical Advisory Board, OASIS (TAB)
>> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>>
>> Another Word For It (blog): http://tm.durusau.net
>> Homepage: http://www.durusau.net
>> Twitter: patrickDurusau
>>
>>


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-15 Thread Christian Grün
Hi Patrick

I noticed that the attributes for the wg element had not been aligned, so I
was wondering if you were thinking of a more advanced rule.

Or would you possibly like to supply the names of the elements for which
the alignment should take place?

Best,
Christian



Patrick Durusau  schrieb am Mi., 15. Feb. 2023, 03:51:

> Christian,
>
> Ah, no, it isn't a length of element name + attribute but the ability to
> align attributes for an element as you see in my post for the  element. Each key/value is followed by a line return.
>
> In the mean time, the current version of tidy has been added to the
> workflow to produce the desired results.
>
> But it would be great to have it native to BaseX!
>
> Thanks!
>
> Patrick
>
> On 2/14/23 01:30, Christian Grün wrote:
> > Hi Patrick,
> >
> > There’s currently no serialization parameter to control the custom
> > indentation of attributes.
> >
> > If I get you correctly, you’d like to get attributes indented if the
> > string length of the element name and the attributes exceed a specific
> > maximum length?
> >
> > Best,
> > Christian
> >
> >
> > On Mon, Feb 13, 2023 at 9:10 PM Patrick Durusau 
> wrote:
> >> Greetings!
> >>
> >> I've been tasked with using BaseX to produce:
> >>
> >> *
> >>
> >>
> >>   
> >>   rule="Np-Appos">
> >>  >>after=" "
> >>class="noun"
> >>gbiType="proper"
> >>xml:id="n57001001001"
> >>lemma="Παῦλος"
> >>normalized="Παῦλος"
> >>strong="3972"
> >>number="singular"
> >>gender="masculine"
> >>case="nominative"
> >>gloss="Paul"
> >>domain="093001"
> >>ln="93.294a"
> >>morph="N-NSM"
> >>unicode="Παῦλος">Παῦλος
> >>
> >> *
> >>
> >> The indenting is easy enough and I can even make it deeper if required
> >> but is there a command for serialization that will properly format the
> >> attributes?
> >>
> >> My personal suspicion is that inserting \n when each attribute is
> >> serialized (and not on the last one) is the easier route but I promised
> >> to investigate the command line.
> >>
> >> Have I overlooked something in the very fine manual?
> >>
> >> Hope everyone is having a great week!
> >>
> >> Patrick
> >>
> >> --
> >> Patrick Durusau
> >> patr...@durusau.net
> >> Technical Advisory Board, OASIS (TAB)
> >> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
> >> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
> >>
> >> Another Word For It (blog): http://tm.durusau.net
> >> Homepage: http://www.durusau.net
> >> Twitter: patrickDurusau
> >>
> --
> Patrick Durusau
> patr...@durusau.net
> Technical Advisory Board, OASIS (TAB)
> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>
> Another Word For It (blog): http://tm.durusau.net
> Homepage: http://www.durusau.net
> Twitter: patrickDurusau
>
>


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-14 Thread Patrick Durusau

Christian,

Ah, no, it isn't a length of element name + attribute but the ability to 
align attributes for an element as you see in my post for the element. Each key/value is followed by a line return.


In the mean time, the current version of tidy has been added to the 
workflow to produce the desired results.


But it would be great to have it native to BaseX!

Thanks!

Patrick

On 2/14/23 01:30, Christian Grün wrote:

Hi Patrick,

There’s currently no serialization parameter to control the custom
indentation of attributes.

If I get you correctly, you’d like to get attributes indented if the
string length of the element name and the attributes exceed a specific
maximum length?

Best,
Christian


On Mon, Feb 13, 2023 at 9:10 PM Patrick Durusau  wrote:

Greetings!

I've been tasked with using BaseX to produce:

*

   
  
 
Παῦλος

*

The indenting is easy enough and I can even make it deeper if required
but is there a command for serialization that will properly format the
attributes?

My personal suspicion is that inserting \n when each attribute is
serialized (and not on the last one) is the easier route but I promised
to investigate the command line.

Have I overlooked something in the very fine manual?

Hope everyone is having a great week!

Patrick

--
Patrick Durusau
patr...@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau


--
Patrick Durusau
patr...@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau



OpenPGP_signature
Description: OpenPGP digital signature


Re: [basex-talk] Formatting attributes as an indented list?

2023-02-14 Thread Hans-Juergen Rennau
 A call from the backbench: I think it would be interesting to have such a 
serialization option! The esthetic aspect of XML can be important, depending on 
context. What we get without such an option looks like a heap of information.
      
      Παῦλος      



Am Dienstag, 14. Februar 2023 um 07:30:46 MEZ hat Christian Grün 
 Folgendes geschrieben:  
 
 Hi Patrick,

There’s currently no serialization parameter to control the custom
indentation of attributes.

If I get you correctly, you’d like to get attributes indented if the
string length of the element name and the attributes exceed a specific
maximum length?

Best,
Christian


On Mon, Feb 13, 2023 at 9:10 PM Patrick Durusau  wrote:
>
> Greetings!
>
> I've been tasked with using BaseX to produce:
>
> *
>
>          
>              
>                
>                                          after=" "
>                      class="noun"
>                      gbiType="proper"
>                      xml:id="n57001001001"
>                      lemma="Παῦλος"
>                      normalized="Παῦλος"
>                      strong="3972"
>                      number="singular"
>                      gender="masculine"
>                      case="nominative"
>                      gloss="Paul"
>                      domain="093001"
>                      ln="93.294a"
>                      morph="N-NSM"
>                      unicode="Παῦλος">Παῦλος
>
> *
>
> The indenting is easy enough and I can even make it deeper if required
> but is there a command for serialization that will properly format the
> attributes?
>
> My personal suspicion is that inserting \n when each attribute is
> serialized (and not on the last one) is the easier route but I promised
> to investigate the command line.
>
> Have I overlooked something in the very fine manual?
>
> Hope everyone is having a great week!
>
> Patrick
>
> --
> Patrick Durusau
> patr...@durusau.net
> Technical Advisory Board, OASIS (TAB)
> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>
> Another Word For It (blog): http://tm.durusau.net
> Homepage: http://www.durusau.net
> Twitter: patrickDurusau
>
  

Re: [basex-talk] Formatting attributes as an indented list?

2023-02-13 Thread Christian Grün
Hi Patrick,

There’s currently no serialization parameter to control the custom
indentation of attributes.

If I get you correctly, you’d like to get attributes indented if the
string length of the element name and the attributes exceed a specific
maximum length?

Best,
Christian


On Mon, Feb 13, 2023 at 9:10 PM Patrick Durusau  wrote:
>
> Greetings!
>
> I've been tasked with using BaseX to produce:
>
> *
>
>   
>  
> 
>   after=" "
>   class="noun"
>   gbiType="proper"
>   xml:id="n57001001001"
>   lemma="Παῦλος"
>   normalized="Παῦλος"
>   strong="3972"
>   number="singular"
>   gender="masculine"
>   case="nominative"
>   gloss="Paul"
>   domain="093001"
>   ln="93.294a"
>   morph="N-NSM"
>   unicode="Παῦλος">Παῦλος
>
> *
>
> The indenting is easy enough and I can even make it deeper if required
> but is there a command for serialization that will properly format the
> attributes?
>
> My personal suspicion is that inserting \n when each attribute is
> serialized (and not on the last one) is the easier route but I promised
> to investigate the command line.
>
> Have I overlooked something in the very fine manual?
>
> Hope everyone is having a great week!
>
> Patrick
>
> --
> Patrick Durusau
> patr...@durusau.net
> Technical Advisory Board, OASIS (TAB)
> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>
> Another Word For It (blog): http://tm.durusau.net
> Homepage: http://www.durusau.net
> Twitter: patrickDurusau
>