Forskjeller

Her vises forskjeller mellom den valgte versjonen og den nåværende versjonen av dokumentet.

--- akkorder:test [d.m.Y H:i] – admin
+++ akkorder:test [d.m.Y H:i] – admin
@@ Linje 1: / Linje 1: @@
-====== Same chord rendered differently ======
+====== Same grip... two diagrams? ======
-Seems to be two separate mechanisms for rendering chords?
+The A chord diagram rendered via the regular JTab chord syntax (RCS):
+<html><div class="jtab">A</div></html>
-<html><div class="jtab"> A E7sus4 </div></html>
+The A chord diagram rendered via the custom JTab JS chord syntax - (CCS).
 %0/0.0/0.2/2.2/3.2/4.0/0[A]
+In RCS the ''class="jtab rendered"'' is in a ''div'' tag
-====== Each chord, separate block element ======
+In CCS the ''class="jtab rendered"'' is in a ''span'' tag
-With the single chord syntax, each chord resides in a separate HTML block element.
-There's a separate "''jtab render''" span tag, "''builder''"-id div tag and svg tag for each chord.
+====== Each chords... separate block element ======
+In CCS each chord diagram is rendered inside separate HTML block elements.
+There's a separate ("''jtab render''" <wrap em>SPAN</wrap> tag), "''builder''"-id div tag and ''svg'' tag for each chord.
@@ Linje 31: / Linje 36: @@
+====== Layout - new line or not ======
+It would be nice if diagram could be laid out on one line just by using carriage return or new line"...
-A great thing is if you could get more than one chord diagram on one line, and use carriage return / new line to change that.
+Using ''div class="jtab chordonly"'' notation within html-tags in dokuwiki (with the "htmlok" configured to yes in dokuwiki), you have to use a separate div for each line.
+<html>
+<div class="jtab chordonly">
+%5/3.X/X.3/1.4/2.3/1.X/X[Bm7b5] /
+%7/2.X/X.7/3.7/4.6/1.X/X[Bm7b5] /
+%10/2.X/X.9/1.10/3.10/4.X/X[Bm7b5] /
+%13/2.X/X.12/1.14/3.12/1.X/X[Bm7b5] / ||
+</div>
+</html>
+<html>
+<div class="jtab chordonly">
+%X/X.X/X.3/1.4/2.3/1.5/4[Bm7b5] /
+%X/X.X/X.7/2.7/3.6/1.7/4[Bm7b5] /
+%X/X.X/X.9/1.10/3.10/3.10/3[Bm7b5] /
+%X/X.X/X.12/1.14/3.12/1.13/2[Bm7b5] / ||
+</div>
+</html>
+<html>
+<div class="jtab chordonly">
+%X/X.2/2.X/X.2/3.3/4.1/1[Bm7b5] /
+%X/X.5/2.X/X.4/1.6/4.5/3[Bm7b5] /
+%X/X.8/2.X/X.7/1.10/4.7/1[Bm7b5] /
+%X/X.12/3.X/X.10/1.12/4.10/1[Bm7b5] / ||
+</div>
+</html>
+<html>
+<div class="jtab chordonly">
+%1/1.2/2.X/X.2/3.3/4.X/X[Bm7b5] /
+%5/2.5/3.X/X.4/1.6/4.X/X[Bm7b5] /
+%7/1.8/2.X/X.7/1.10/4.X/X[Bm7b5] /
+%10/1.12/3.X/X.10/1.12/4.X/X[Bm7b5] / ||
+</div>
+</html>
+Here the class is ''jtab chordonly rendered''.
 ====== 1 - Slash chord name & layout ======
-I'm not a programmer but there seems to be some conflict between the chord name syntax in the "Custom Chord Notation" (CCN) and the regular Chord Notation (CN) of the script. When a CCN chord name contains a slash [A/E] or a spaces or separated letters, the CNN chord name as CN syntax.
+There seems to be some conflict between the chord name syntax in the "Custom Chord Notation" (CCN) and the regular Chord Notation (CN). As soon as CCN chord name contains a slash [A/E] or a spaces or a space pluss another letter, the CNN chord name seems to be interpreted as CN syntax.
@@ Linje 256: / Linje 313: @@
 %3/3.X/X.3/4.2/2.1/1.1/1[G9sus]
-<html>
-<div class="jtab chordonly">
-%5/3.X/X.3/1.4/2.3/1.X/X[Bm7b5] /
-%7/2.X/X.7/3.7/4.6/1.X/X[Bm7b5] /
-%10/2.X/X.9/1.10/3.10/4.X/X[Bm7b5] /
-%13/2.X/X.12/1.14/3.12/1.X/X[Bm7b5] / ||
-</div>
-</html>
-<html>
-<div class="jtab chordonly">
-%X/X.X/X.3/1.4/2.3/1.5/4[Bm7b5] /
-%X/X.X/X.7/2.7/3.6/1.7/4[Bm7b5] /
-%X/X.X/X.9/1.10/3.10/3.10/3[Bm7b5] /
-%X/X.X/X.12/1.14/3.12/1.13/2[Bm7b5] / ||
-</div>
-</html>
-<html>
-<div class="jtab chordonly">
-%X/X.2/2.X/X.2/3.3/4.1/1[Bm7b5] /
-%X/X.5/2.X/X.4/1.6/4.5/3[Bm7b5] /
-%X/X.8/2.X/X.7/1.10/4.7/1[Bm7b5] /
-%X/X.12/3.X/X.10/1.12/4.10/1[Bm7b5] / ||
-</div>
-</html>
-<html>
-<div class="jtab chordonly">
-%1/1.2/2.X/X.2/3.3/4.X/X[Bm7b5] /
-%5/2.5/3.X/X.4/1.6/4.X/X[Bm7b5] /
-%7/1.8/2.X/X.7/1.10/4.X/X[Bm7b5] /
-%10/1.12/3.X/X.10/1.12/4.X/X[Bm7b5] / ||
-</div>
-</html>