Peter Dell

That would break compatibility. Having the 40 character ATASCII restriction in the Tags, file names and folder names is a good thing. ´That's why I keep a 2nd file with Unicode mappings (and more) of the composers. So maybe for a start, could we have something like the lookup searching for "STIL*.txt"? Then I can play around the generating STIL without harming the manually edited file.

I originally opted for STIL information in SAP files as extra tags. Ok, then I understood this differently/wrong: https://asma.scene.pl/wiki/StilVsExtraSapTags I thought, you were against adding that information to SAP in first place. A huge benefit I see in having separate file/files is that they can support unicode (which is something we already use a log in the STIL.txt). We cannot have unicode inside SAP. Other than that, I'd find self-contained files the optimum. Base on my experience of the...

I originally opted for STIL information in SAP files as extra tags. Ok, then I understood this different/wrong: https://asma.scene.pl/wiki/StilVsExtraSapTags I though you were against adding that information to SAP in first place. A huge benefit I see in having separate file/files is that they can support unicode (which is something we already use a log in the STIL.txt). We cannot have unicode inside SAP. Other than that I'd find self-contained files the optimum. Base on my experience of the past...

Support STIL information in ".stil" co-files

Check added with https://github.com/asma-atari-org/asma.atari.org/commit/7a65eee0e617c576ffbd0a276207ddd2fa4eb670

I only asked, because the STIL spec actually does not state anything about the path length explicitly. Only the tags ( "COMMENT: ") which are all 9 characters and the values (which are at most 90 characters) are mentioned. Effectively, the HVSC STIL uses 78 characters per line. I also didn't mean to change the limit, but add instead a check on my side, if there is a defined limit. I've added the details to https://asma.scene.pl/wiki/StilVsExtraSapTags How about "Anschuetz_E_and_Weisgerber_J_and_Anschuetz_R"...

I only asked, because the STIL spec actually does not state anything about the path length explicitly. Only the tags ( "COMMENT: ") which are all 9 characters and the values (which are at most 90 characters) are mentioned. Effectively, the HVSC STIL uses 78 characters per line. I also didn't mean to change the limit, but add instead a check on my side, if there is a defined limit. I've added the details to https://asma.scene.pl/wiki/StilVsExtraSapTags How about "Anschuetz_E_and_Weisgerber_J_and_Anschuetz_R"...

I only asked because the STIL spec actually does not state anything about the path length. Only the tags ( "COMMENT: ") which are all 9 characters and the values (which are at most 90 characters) are mentioned. Effectively, the HVSC STIL uses 78 characters per line. I also didn't mean to change the limit, but add instead a check on my side, if there is a defined limit. I've added the details to https://asma.scene.pl/wiki/StilVsExtraSapTags How about "Anschuetz_E_and_Weisgerber_J_and_Anschuetz_R"...