OASIS Open Document Format for Office Applications (OpenDocument) TC

Greetings!

I may have found an issue with the current schema with regard to:

On 16/11/06, Patrick Durusau 

Dave,

Dave Pawson wrote:

> On 16/11/06, Patrick Durusau 

On 16/11/06, Patrick Durusau 

Dave,

Dave Pawson wrote:

> On 16/11/06, Patrick Durusau 

Hi,

It seems to me that the "45pp" example in section 7.8.1 in fact is a 
translation of the German "45ff". Unfortunately, it is not sufficient to 
  change the example to either "XML 45-48 passim" or "XML, pp. 45-48", 
because the description of the "text:combine-entries-with-pp" states

"As the start number with a pp label, or the appropriate label for the 
chosen language, using the text:combine-entries-with-pp attribute"

This means that we have a restriction for the start number here. We have 
(at least) to options to resolve this.

a) We allows language specific either a start number, or a range.

b) We keep the attribute as it is, but explicitly specify that a page 
range is displayed if the text:combine-entries-with-dash attribute has 
the value true.

Best regards

Michael




Patrick Durusau wrote:
> Dave,
> 
> Dave Pawson wrote:
> 
>> On 16/11/06, Patrick Durusau 

On 24/11/06, Michael Brauer - Sun Germany - ham02 - Hamburg

>
> This means that we have a restriction for the start number here. We have
> (at least) to options to resolve this.
>
> a) We allows language specific either a start number, or a range.

Is an I18N solution acceptable?
E.g. the UK one might be
pagerange= pp{0}-{1}
the de might be
pagerange={0}ff

etc


HTH

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Hi Dave,

Dave Pawson wrote:
> On 24/11/06, Michael Brauer - Sun Germany - ham02 - Hamburg
> 
>>
>> This means that we have a restriction for the start number here. We have
>> (at least) to options to resolve this.
>>
>> a) We allows language specific either a start number, or a range.
> 
> Is an I18N solution acceptable?

Yes. Instead of "language specific" I should have said "locale specific".

> E.g. the UK one might be
> pagerange= pp{0}-{1}
> the de might be
> pagerange={0}ff
> 
> etc
> 
> 
> HTH
> 
Michael

Hi,

as agreed, below is my proposal for changing the description of

8.8.1.4 Combining Entries.

The current description is:

[...]

The pages referenced by a combined entry can be formatted as:

- As a range of numbers separated by a dash using the
   text:combine-entries-with-dash attribute.
- As the start number with a pp label, or the appropriate label
   for the chosen language, using the text:combine-entries-with-pp
   attribute.

I propose that we change the last sentence to:

- As the start number, followed by a "ff", or the appropriate label
   for the chosen language, using the text:combine-entries-with-pp
   attribute.

I further propose that we replace "XML 45pp" in table 13 with "XML 45ff".

Best regards

Michael




Michael Brauer - Sun Germany - ham02 - Hamburg wrote:
> Hi,
> 
> It seems to me that the "45pp" example in section 7.8.1 in fact is a 
> translation of the German "45ff". Unfortunately, it is not sufficient to 
>  change the example to either "XML 45-48 passim" or "XML, pp. 45-48", 
> because the description of the "text:combine-entries-with-pp" states
> 
> "As the start number with a pp label, or the appropriate label for the 
> chosen language, using the text:combine-entries-with-pp attribute"
> 
> This means that we have a restriction for the start number here. We have 
> (at least) to options to resolve this.
> 
> a) We allows language specific either a start number, or a range.
> 
> b) We keep the attribute as it is, but explicitly specify that a page 
> range is displayed if the text:combine-entries-with-dash attribute has 
> the value true.
> 
> Best regards
> 
> Michael
> 
> 
> 
> 
> Patrick Durusau wrote:
>> Dave,
>>
>> Dave Pawson wrote:
>>
>>> On 16/11/06, Patrick Durusau 

Patrick Durusau said:
> > That doesn't look right so I checked in the 15th Edition of the Chicago
> > Manual of Style,

Dave Pawson:
> If you could name a reference that applies equally to all nations
> I guess that would apply.

I may be misunderstanding this comment, but in my mind,
any indexing system must be flexible enough to handle
the UNION of all common manuals of style.
Whether they apply to every nation or not.

The SCHEMA should apply equally to all nations, YES.
But that means that the schema must be sufficiently
flexible to capture the needs of every nation - and different
nations (and communities) have different needs.
A list of "common styles" and some complicated samples
might be a good idea, because it's important that the
resulting schema be able to handle ALL of them.

--- David A. Wheeler

On 17/11/06, David A. Wheeler