Bruce D'Arcus

> If we did move `translated` to the title object, I suggest we pull the separate variable from v1.0.2. My impulse is we should do this. The only reason I...

> A `translated` slot in the title object would either require additional forms (`form="translated"`, `form="translated-short"`, `form="translated-main"`, `form="translated-sub"`) or perhaps a new attribute (`translated="true"`). The new attribute might be better (e.g.,...

> `language-alternate` sounds good. Or what about `language-alternative`? I'm agnostic. > In terms of structure, it should mirror the standard structure of title variables This attribute is broader, and it's...

> Whether it's a translation or transliteration is clear from the language code. How so? You mean by virtue of it being under an `alternate-language` property?

Can you point to a style that demonstrates this problem? On Sep 29, 2011 5:11 PM, "Frank Bennett" < [email protected]> wrote: > In note styles, the formatting of entries in...

I generally have the same reaction as @rmzelle - seems reasonable enough, but I do wonder if it might have negative unintended consequences, and whether the potential benefits outweigh the...

Not 100% sure, but I _think_ it'd be fine to allow. WDYT?

His main concern there is validation, which isn't something to worry about for us. If a style author has typos that lead to bad output, that's their problem; not our's....

These properties, and this citation schema, is for interactive GUI apps really; not batch processors. And yeah, for Zotero, Mendeley, etc., seems there should just be one way to do...

I'm really asking the question of Zotero and Mendeley folks.