[tei-council] Minor error in Guidelines

[Kevin Hawkins]

Good, I've updated 
http://www.tei-c.org/Activities/Council/Working/tcw20.xml .

On 1/27/12 12:38 PM, Rebecca Welzenbach wrote:
> I would certainly find it valuable!
>
> On Thu, Jan 26, 2012 at 8:13 PM, Kevin Hawkins
> <kevin.s.hawkins at ultraslavonic.info>  wrote:
>> I'm wondering whether others feel that we should add a bit to
>>
>> http://www.tei-c.org/Activities/Council/Working/tcw20.xml
>>
>> or perhaps more properly
>>
>> P5/Source/Guidelines/en/style-guide.txt
>>
>> stating this distinction.  There might be other things that those who
>> have been editing the Guidelines keep in mind but haven't written down
>> for the rest of us.
>>
>> Such a passage would be similar to this, which I found in tcw20 and is
>> similarly prescriptive about encoding practice:
>>
>> ###
>>
>> In most chapters, the two character code is also used as a prefix for
>> the @xml:id values given to each<div>  element. Note that every<div>
>> element carries an @xml:id value, whether or not it is actually
>> referenced explicitly elewhere in the Guidelines.
>>
>> ###
>>
>> Is this worthwhile, or would none of us ever remember to consult this
>> anyway?
>>
>> --K.
>>
>> On 1/13/12 11:19 AM, Lou Burnard wrote:
>>> In the Guidelines, as elsewhere,
>>>
>>> <ref target="#foo">section foo</ref>    means: generate a link to #foo and
>>> represent it by the text "section foo".
>>>
>>> <ptr target="#foo"/>    means: generate a link to #foo and represent it by
>>> whatever text your processor chooses to generate
>>>
>>>
>>>
>>> On 13/01/12 16:17, Martin Holmes wrote:
>>>> Could you clarify what the difference is between using<ref>     and<ptr>
>>>> in the guidelines?
>>>>
>>>> Cheers,
>>>> Martin
>>>>
>>>> On 12-01-13 01:32 AM, Sebastian Rahtz wrote:
>>>>>
>>>>> On 13 Jan 2012, at 05:01, Martin Holmes wrote:
>>>>>
>>>>>> I've put in a bug report for this:
>>>>>>
>>>>>> <http://purl.org/TEI/BUGS/3473329>
>>>>>>
>>>>>> The basic problem is that in the web view of the Guidelines, figures
>>>>>> within each chapter are numbered 1, 2, 3, 4 etc., but in the PDF output,
>>>>>> they're numbered 11.1, 11.2, 11.3…
>>>>>>
>>>>> there are two issues here.
>>>>>
>>>>>       a) the use of dangerous markup like "<ref target="#sleeprs">figure 4 above</ref>", which should be changed into a<ptr>      to avoid this sort of problem
>>>>>       b) the different numbering schemes
>>>>>
>>>>> for the latter, which do we want for the Guidelines? by chapter, or sequential throughout?
>>>>>
>>>>> for the former, I found 3 occurrences of this, and changed them to<ptr>. am testing before committing.
>>>>> --
>>>>> Stormageddon Rahtz
>>>>> Head of Information and Support Group
>>>>> Oxford University Computing Services
>>>>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>>>>
>>>>> Sólo le pido a Dios
>>>>> que el futuro no me sea indiferente
>>>>>
>>>>
>>>
>> --
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived