https://issues.apache.org/bugzilla/show_bug.cgi?id=50730

Igor Galić <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Igor Galić <[email protected]> 2011-02-28 14:25:35 EST 
---
"""Using a type map (i.e., a *.var  file) which names the files containing the
variants explicitly, or"""

and then:

"""Type map files should have the same name as the resource which they are
describing, and have an entry for each available variant; these entries consist
of contiguous HTTP-format header lines."""

If that is not clear enough, can you suggest a better phrasing?

For one, for the other: We then go on to describe the multitude of things you
can pack into a single .var file -- I'm not quite clear how from these two
pieces of information you were able to interpret that:

a) type-maps can be placed in arbitrary directories (How then should they be
mapped to the requested resources?)
b) There can be more than one type-map

...sure there can be.. but that would be silly...

You could for instance create

# foo.en.var:
URI: foo.en.html
Content-Encoding: text/html

URI: foo.en.xhtml
Content-Encoding: text/xhtml

# foo.fr.var:
URI: foo.fr.html
Content-Encoding: text/html

URI: foo.fr.xhtml
Content-Encoding: text/xhtml


But that seems silly, since you can vary on all that within the same type-map:

# foo.var:
URI: foo.en.html
Content-Language: en
Content-Type: text/html

URI: foo.en.xhtml
Content-Language: en
Content-Type: text/xhtml

URI: foo.fr.html
Content-Language: fr
Content-Type: text/html

URI: foo.fr.xhtml
Content-Language: fr
Content-Type: text/xhtml

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to