Parsoid/Language conversion/Chat with Liangent

Jump to navigation Jump to search

Chat with Liangent[edit]

[08:56] <liangent> -{foo}- means "foo" outputted literally. no further conversion happens on it
[08:56] <gwicke> ahhhhh
[08:56] <gwicke> that's the misunderstanding
[08:56] <subbu> liangent, interesting ... so, the next qn. is even more basic and unrelated to parsing ... is there a wiki page you can point me to that will explain the reasons for auto-conversion, etc.?
[08:57] <subbu> gwicke, we understood it the opposite :)
[08:57] <gwicke> yup
[08:57] <gwicke> so this makes sense now
[08:58] <liangent> subbu: have you read this?
[08:58] <subbu> no, thanks.  that is useful.
[08:59] <liangent> the "implementation" section is outdated
[08:59] <gwicke> liangent: I was chatting with some google folks two weeks ago about the same problem btw- they also need to do variant conversions and are considering to use their own translate tool for it
[09:00] <gwicke> but are considering to adapt our code too
[09:00] <gwicke> so I guess we'll simply pass through content and mark -{ }- as conversion-protected
[09:01] <liangent> google's translator is said to be based on statistic -- like what they do for web pages
[09:01] <liangent> mw's translator is based on manually composed dictionary -- like what we do for wikipedia
[09:01] <gwicke> *nod*
[09:03] <gwicke> we'll try to represent the conversion protection so that moving such protected content around preserves the protection
[09:03] <gwicke> somewhat similar to noinclude and onlyinclude sections inside a content page
[09:03] <liangent> so how do you want to display these blocks
[09:04] <subbu> gwicke, right, that part doesn't change.
[09:04] <liangent> sometimes they generate output (and sometimes thet don't
[09:04] <gwicke> liangent: we don't plan to add visible differences, but we'll add the information in attributes
[09:04] <gwicke> the VE can then figure out how to indicate conversion protection
[09:05] <liangent> ok leave this pain to VE team then :)
[09:05] <gwicke> the -{}- trick might deserve its own meta tag
[09:06] <liangent> but this is not enough for phase 3 (as I described in )
[09:06] <gwicke> so that the VE can render an icon
[09:07] <liangent> yeah let me give some quick descriptions of the -{ }- markup
[09:08] <liangent> first, a generic -{ X }- tag outputs X, if the tag doesn't match anything else
[09:08] <gwicke> liangent: is there documentation on this somewhere?
[09:09] <liangent> yeah but it's only in Chinese afaik
[09:09] <gwicke> ah, that explains why we have not found it yet ;)
[09:10] <liangent> maybe I can just make a quick translation for me
[09:10] <liangent> *for you
[09:10] <liangent> with examples stripped
[09:10] <gwicke> just a short section on how the syntax can be used would be great
[09:13] <gwicke> I found this comment:
[09:13] <gwicke> * Syntax of the markup:
[09:13] <gwicke> * -{code1:text1;code2:text2;...}-  or
[09:13] <gwicke> * -{flags|code1:text1;code2:text2;...}-  or
[09:13] <gwicke> * -{text}- in which case no conversion should take place for text
[09:13] <liangent> right but there're more
[09:14] <liangent> like -{H|text1=>zh-cn:text2;}-
[09:14] <liangent> or -{zh-hans;zh-hant|text}-
[09:14] <gwicke> what is the meaning of code1:text1?
[09:14] <gwicke> convert from code1 to target for text1?
[09:14] <liangent> it should be something like -{zh-cn:text1;zh-tw:text2;...}-
[09:15] <liangent> and it displays text1 for zh-cn users, or text2 for zh-tw users
[09:15] <gwicke> ah, explicit manual overrides
[09:16] <gwicke> that might be tricky for the editor
[09:17] <gwicke> can there be -{code1:<table>.....</table>;code2:<div>..</div>}-?
[09:17] <liangent> I know, but it's not difficult to describe in DOM
[09:17] <liangent> yes it can
[09:17] <gwicke> ouch
[09:17] <gwicke> I feared that this would be the case
[09:18] <gwicke> and of course the contents don't need to be balanced
[09:18] <gwicke> as it is all string-based
[09:18] [Notify] brion went offline (
[09:18] <liangent> in practice it's rarely unbalanced
[09:18] <liangent> but technically it's completely possible
[09:18] <subbu> gwicke, we can treat those as independent parsing contexts
[09:18] <subbu> similar to how extensions/include tag content is handled in tokenizer
[09:18] <gwicke> yes, we should really
[09:19] <gwicke> and possibly represent the variants as sub-doms marked with the language
[09:19] <subbu> we've figured out hierarchical parsing scopes in the tokenizer and we just apply it wherever possible.
[09:20] <gwicke> or as html in attributes (not pretty, but might avoid rendering issues)
[09:21] <gwicke> we don't want all variants to show up / be indexed at once
[09:21] <liangent> gwicke: subbu: do you want to see this?
[09:21] <liangent> zh-cn users see a blue box, while zh-tw users see a red one...
[09:22] <subbu> i still think we start drawing up wikitext constructs that we consider deprecated uses -- and a good subproject for someone would be use info in dom based on auto-correct and other flags to signal "deprecated/erroneous wikitext" to editors .. kind of a linting tool.
[09:22] <subbu> but not sure we have the bandwidth to do it :)
[09:22] <gwicke> probably not before the July release
[09:22] <subbu> seems like a far out project.
[09:22] <subbu> definitely not!
[09:22] <gwicke> GSOC next year ;)
[09:23] --> spectie has joined this channel (~fran@***).
[09:23] <-- spectie has left this server (Changing host).
[09:23] --> spectie has joined this channel (~fran@unaffiliated/spectie).
[09:23] <gwicke> so I found some docs on the flags:
[09:23] <gwicke> 'A' => 'A',  // add rule for convert code (all text convert)
[09:23] <gwicke> 'T' => 'T',  // title convert
[09:23] <gwicke> 'R' => 'R',  // raw content
[09:23] <gwicke> 'D' => 'D',  // convert description (subclass implement)
[09:23] <gwicke> '-' => '-',  // remove convert (not implement)
[09:23] <gwicke> 'H' => 'H',  // add rule for convert code
[09:23] <gwicke>  // (but no display in placed code)
[09:23] <gwicke> 'N' => 'N'  // current variant name
[09:24] <liangent> yep
[09:25] <gwicke> some of these sound like they would affect global converter state?
[09:25] <gwicke> or do these only apply to one block?
[09:25] <subbu> liangent, so, those divs are closed inside each then
[09:25] <gwicke> // 'S' show converted text
[09:25] <gwicke> // '+' add rules for alltext
[09:25] <gwicke> // 'E' the gave flags is error
[09:26] <gwicke> we'll need to understand these flags to be able to represent them sanely I think
[09:27] <liangent> gwicke: it's currently done in this way, but ideally it could be fixed to only modify the state for the current conversion run
[09:28] <liangent> *it's currently done to modify global state
[09:28] <liangent> subbu: I don't really understand your question
[09:29] <gwicke> liangent: global state creates all sorts of problems for us
[09:29] <liangent> gwicke: I haven't seen S/+/E in real world... maybe I have to have a look first
[09:29] <gwicke> we plan to re-render parts of a page, which we can only do if this can be done independent of some magical global state
[09:29] <liangent> gwicke: if you can avoid that ... don't do that in its current php way
[09:30] <gwicke> I doubt that we'll complete this before July then
[09:31] <liangent> gwicke: well you didn't paste the next line "// these flags above are reserved for program"
[09:31] <gwicke> we'd have to convert a delta encoding to a list of options per block
[09:32] <gwicke> ok, so 'A' etc are not used in wikitext
[09:33] <liangent> after I read the code ...
[09:33] <gwicke> which flags are used in wikitext if S/+/E doesn't show up either?
[09:33] <gwicke> would these be the only candidates?
[09:33] <liangent> 'A' is converted to 'S' and '+' internally
[09:34] <liangent> and 'S' is just as if there's no flag
[09:34] <gwicke> ah, that comment refers to the ones before it
[09:34] <gwicke> the comment style in the converter is slightly non-conventional
[09:34] <cscott> it seems like having liangent do a quick translation (and store that on the wiki somewhere) would be useful for future documentation (to en-speaking hackers)
[09:35] <gwicke> yes, that would be great
[09:35] <liangent> gwicke: it was written years ago and almost no one modernize it
[09:36] <gwicke> even a link to the Chinese documentation might be useful
[09:36] <gwicke> could feed that through a translate tool
[09:36] <liangent> I can't find any place really using 'E' except for that comment
[09:36] <liangent> gwicke: you want it?
[09:37] --> lwelling has joined this channel (~owner@wikimedia/lwelling).
[09:37] <gwicke> hmm- didn't google offer website translations at some point?
[09:38] <cscott> gwicke: maybe only if you're using chrome now?
[09:38] <gwicke> looks like they made that a commercial service
[09:38] <cscott> google translate was one of their deprecated labs apis, but then they undeprecated it
[09:38] <cscott> but presumably with some tos changes
[09:39] * gwicke tries bing
[09:39] <gwicke>
[09:41] <gwicke>
[09:41] --> Reedy_ has joined this channel (~quassel@wikimedia/
[09:41] <gwicke> pasting a url into produces a clickable url as the translation
[09:41] <cscott> should we add those links (and liangent's translation) to ?
[09:42] <liangent> cscott: no
[09:42] <liangent> should be a page on
[09:42] <gwicke> yeah, software docs should be on
[09:43] <gwicke> we initially used meta for software too, before existed
[09:43] <-- Reedy has left this server (Ping timeout: 258 seconds).
[09:44] <cscott> liangent's translation would be appreciated; the auto-translated version is not very intelligible
[09:46] <cscott> although sometimes amusingly misleading "-{foo}-" means emits "foo" literally --> becomes "a total ban on the word conversion, in some cases (such as just where prohibited word conversion)"
[09:46] <liangent> cscott: is the "syntax" section enough?
[09:46] <liangent> it gives some usage examples
[09:46] <cscott> when i first read that, i thought it was referring to censoring out expletives ("prohibited words")
[09:46] <cscott> liangent: i think so. it's hard to know what's important from the other parts w/o understanding what they are trying to say ;)
[09:47] <cscott> i'll trust your judgement
[09:47] <-- HaeB has left this server (Ping timeout: 264 seconds).
[09:49] <cscott> like, the first two paragraphs *seem* to be boilerplate about web standards and markup.  if there's some actual interesting point in there, a translation would be nice.  (what does "wikitext also no clear definition of normalized work is still in progress, which mark is the label unclear" mean?)
[09:49] * cscott -> lunch
[09:50] * gwicke -> office ;)
[09:50] <cscott> if brion is easily-pokable, i hope the latest core patch will finally put the manual thumbs to rest
[09:50] <gwicke> I'm out of poking distance right now, but that will change in about 15 minutes
[09:50] <cscott> thx
[09:51] <cscott> i'm tired of that patchset
[09:51] <gwicke> ;)
[10:11] [Notice] -NickServ- This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>.
[10:11] [Notice] -NickServ- You are now identified for gwicke.
[10:11] [Notice] -MemoServ- You have 1 new memo.
[10:11] [Notice] -MemoServ- To read them, type /msg MemoServ READ NEW
[10:11] [Error] No such nick/channel.
[10:11] --> You have joined the channel #mediawiki-parsoid (~gabriel@wikimedia/gwicke).
[10:11] *** The channel topic is "Round-tripping parser and runtime for MediaWiki | gwicke, subbu, marktraceur, and awight are the team | | always fresh round-trip testing results at".
[10:11] *** The topic was set by Brooke!sex@wikipedia/MZMcBride on 27.11.12 14:39.
[10:12] *** Channel modes: no colors allowed, no messages from outside
[10:12] *** This channel was created on 19.09.12 16:31.
[10:14] --> HaeB has joined this channel (~quassel@wikipedia/HochaufeinemBaum).
[10:17] *** rmoen|afk is now known as rmoen.
[10:21] <gerrit-wm> New patchset: Subramanya Sastry; "WTS Code cleanup: Simplify calls to serializeChildren" [mediawiki/extensions/Parsoid] (master) -
[10:25] *** Trevor|afk is now known as TrevorParscal.
[10:25] [Notify] TrevorParscal is online (
[10:25] <-- gerrit-wm has left this server (Remote host closed the connection).
[10:25] --> gerrit-wm has joined this channel (
[10:32] <-- HaeB has left this server (Read error: Connection reset by peer).
[10:34] <marktraceur> cscott: We haven't figured it out yet (I dunno if anyone answered)
[10:34] <-- hashar has left this server (Quit: I am a manual virus, please copy me to your quit message.).
[10:36] [Notify] brion is online (
[10:37] --> diiq has joined this channel (c7bcc109@gateway/web/freenode/ip.***).
[10:46] <cscott> marktraceur: ok, i'm going to document how image tags currently work; hopefully that will get pushed quickly so you can patch the tests as well as the source when you make your changes
[10:46] <liangent> cscott:
[10:48] <liangent> you might be interested in - will implementing this be useful for parsoid team>
[10:48] <cscott> could we do bidirectional links with the chinese source for the page?
[10:48] <cscott> might make it slightly more likely they will get updated when changes are made
[10:49] *** zz_YuviPanda is now known as YuviPanda.
[10:49] <cscott> the variant bug does look interesting; it would be a decent way to get more i18n tests into parsertests
[10:50] <cscott> currently parsertests relies on the kaa wiki
[10:50] * cscott loves non-roman script languages
[10:50] <liangent> cscott: and mw core parser tests use language=sr and language=zh for the converter
[10:52] <cscott> ah, i see that now
[10:52] <liangent> crosswiki link done
[10:52] <cscott> i didn't read that section as closely; i was working on linktrail/linkprefix bugs at the time
[10:53] <cscott> i didn't parse the variant= option to parserTests when I implemented language= support for parsoid, maybe i should do that
[10:53] <cscott> of course, that requires grokking variants fully first, which it looks like gwicke is much closer to having done
[10:54] <liangent> if you read that parserTest file ... you need to make sure that you can recognize chinese characters
[10:55] <liangent> though some of tests are in sr -- which requires cyrl
[10:57] <liangent> cscott: TBH conversion between roman scripts are more difficult, because you must be careful not to touch html tags etc.
[10:57] <liangent> which is never a problem when you convert Chinese
[10:58] <cscott> my evil long-term plan is to have parsoid pass all the parser tests
[10:58] <cscott> so i should take a closer look and see which variant tests are passing/failing
[10:58] <cscott> it doesn't seem like character set should really be an issue.  UTF8 FTW.
[10:58] <liangent> I believe all variant tests are failing
[10:59] <liangent> you must be echoing -{}- currently
[10:59] <cscott> i should have said, "after we parse the variant= option" -- they are certainly failing now because we're just ignoring the language variant
[10:59] <liangent> ah
[11:00] <cscott> can you point to the specific test you're thinking of when you say, "TBH conversion between roman scripts are more difficult, because you must be careful not to touch html tags etc."
[11:00] <cscott> i think I also need the TBH TLA expanded
[11:01] <liangent> to be honest
[11:03] <cscott> oh, right, i see now
[11:03] <cscott> i was trying to make this more complicated than it is
[11:04] <cscott> yeah, parsoid doesn't really have much problem with separating out the markup, that's all general and done before we'd look at the characters
[11:05] <cscott> we have more of a problem making sure we're using the right localized configuration, especially with all the crazy fallback and inheritance stuff that goes on in core
[11:07] <liangent> sadly zh has so much such stuff, even only in the converter part
[11:07] <liangent> see that table I translated just now
[11:07] <liangent> for example, zh-cn reuses rules from zh-hans but doesn't reuse everything...
[11:08] *** edsanders is now known as edsanders|away.
[11:12] <cscott> wow, there are a lot of zh-* codes which I wouldn't think of as "chinese" as all.
[11:13] <cscott> zh-min, for example -- shouldn't that be a separate language?
[11:15] <liangent> cscott: that's a legacy one. the standard code for it is nan
[11:15] <cscott> so makes it seem like the zh- languages are converging on a zh-{language name}-{country} format
[11:15] * gwicke returns from another interview
[11:15] <liangent> see
[11:16] <liangent> cscott: you mean zh-Hans-CN ?
[11:17] <cscott> zh-hans-cn, zh-gan, zh-min, zh-hakka
[11:17] <cscott> but these might just be legacy names, that bugzilla seems like they've renamed some
[11:17] <cscott> 'nan' makes more sense than zh-min-nan, where 'zh' was really just standing for the character set, not tht language
[11:18] <liangent> zh-hans-cn looks verbose
[11:18] <liangent>
[11:19] <liangent> zh-gan is gan now
[11:19] <liangent> the second should be zh-min-nan not zh-min
[11:20] <liangent> currently it still resides at, but its html says <html lang="nan" dir="ltr" class="client-nojs">
[11:20] <liangent> not sure what zh-hakka is. maybe just hak?
[11:22] <gwicke> do we need to actually implement conversion for successful editing?
[11:22] <gwicke> to me it seems that we mainly need to properly handle conversion tags/blocks
[11:22] <gwicke> without necessarily doing any actualy conversion at first
[11:23] <gwicke> the biggest problem I see is the global nature of conversion rules
[11:24] <gwicke> liangent: will -{zh-hans:computer; zh-hant:ELECTRONICBRAIN;}- cause all instances of ELECTRONICBRAIN to be replaced with computer when converting to hans?
[11:25] <gwicke> or only from that point of the document on, or only inside the block?
[11:27] <liangent> gwicke: yes
[11:28] <liangent> oh no
[11:28] <liangent> no further conversion, unless it has an H or A flag
[11:29] <cscott> do we emit something like <span class="convert"><span class="zh-hans">computer</span><span class="zh-hant">ELECTRONICBRAIN</span></span>, or something like <head><meta type="conversion" lang-from="zh-hans" text-from="computer" lang-to="zh-hant" text-to="ELECTRONICBRAIN"></head>
[11:29] <gwicke> ah, k- and those apply from that point in the document on I guess
[11:31] <cscott> it seems the answer is "the former, unless H is used, in which case it's the latter; unless A is used, in which case it's both"
[11:31] <cscott> i wonder if we could get away with changing the scope of the H and A rules without breaking too many pages
[11:32] <cscott> hoisting them to the nearest enclosing block-level element, or even hoisting them to be per-document, would be much cleaner long-term
[11:32] <cscott> ie, it would be better to have a short table of "additional rules for this page" included in the page's meta-data, like NOTOC and the rest.
[11:32] <liangent> cscott: neither I would say
[11:33] <-- andre__ has left this server (Quit: andre__).
[11:33] <liangent> choose one between <span class="convert" spec="zh-hans:computer; zh-hant:ELECTRONICBRAIN;">computer</span> and <span class="convert" spec="zh-hans:computer; zh-hant:ELECTRONICBRAIN;">ELECTRONICBRAIN</span> based on user's pref
[11:34] <liangent> or if you really want to parse it you can expand the spec to multiple attribs
[11:35] <cscott> i suspect that all user-pref things will get the most general form put into parsoid's output, and then a postprocessor will munge the output for the user's display preferences
[11:35] <cscott> redlinks and stubs would be handled the same way
[11:35] <cscott> date preferences probably too
[11:36] <cscott> the postprocessor might even be client-side javascript or CSS in some cases
[11:36] <liangent> eh ... then just use the current converter as the postprocessor is enough ...
[11:36] <gwicke> yeah, but we should ideally move conversion *rules* to the head
[11:36] <liangent> it's designed to work on HTML currently
[11:37] <cscott> ie, in the <span class="convert"><span class="zh-hans">computer</span><span class="zh-hant">ELECTRONICBRAIN</span></span> example i was assuming the user's stylesheet would display:none one or the other
[11:37] <gwicke> so that they apply to the entire page
[11:37] <liangent> why to the head?
[11:37] <cscott> with some backwards-compatibility selser stuff saying where in the original document the rule was found
[11:37] <gwicke> inline conversion pairs that don't add general rules can be reprocessed independently
[11:38] <gwicke> liangent: so that we can re-process a part of a page correctly
[11:38] <cscott> i think it's also a cleaner representation in the DOM, since HTML doesn't have any "from this point in the document on" state
[11:38] <liangent> not really -- A or H tags don't (technically) affect the whole page
[11:38] <cscott> all DOM attributes are tree-scoped
[11:39] <liangent> it only affects the part after the markup...
[11:39] <gwicke> liangent: is that actually needed?
[11:39] <cscott> liangent: right, that's the part we think we might change (short or long term)
[11:39] <cscott> deprecate
[11:39] <cscott> that's a better word
[11:39] <liangent> hmm there're some real world usage on zhwiki
[11:39] <liangent> primarily used in templates
[11:40] <cscott> the hypothetical GSoC bot could roam through existing wikis and warn of usage that will break
[11:40] <liangent> to avoid pollution of pages using the template
[11:40] <gwicke> ah, we could scope rules to a template I guess
[11:40] <cscott> liangent: the template would add the rule and then remove it?
[11:40] <cscott> yeah, block scoped is fine
[11:40] <gwicke> we parse template independently already
[11:40] <liangent> cscott: yeah
[11:40] <liangent> but it's not always template level
[11:41] <liangent> for some common dictionaries that are not in mediawiki core, we put lots of -{H| }- in some templates
[11:41] <gwicke> liangent: I guess -{ }- can always be used to suppress general rules?
[11:41] <cscott> i guess concretely what i'm saying is that we'd like to deprecate usage which can't be scoped
[11:41] <liangent> then transclude those templates in articles which need that
[11:41] <cscott> gwicke: oh, right -- we can be compatible by adding synthetic blockers to uses of the rule before its "definition"
[11:42] <liangent> gwicke: yes
[11:42] <cscott> but i still feel like the view that VE exposes should be scoped or global; that would be the long-term preferred usage.
[11:42] <gwicke> liangent: if there was an easy way to add those entries globally, would that help?
[11:43] <cscott> or an easy way to add those entries to a given page
[11:43] <gwicke> with globally, I mean for the entire wiki
[11:44] <liangent> gwicke: no. those rules are transcluded when really needed, and usually group by article scope, eg IT, Movie, Sport etc
[11:44] <gwicke> in a way that can also make it easy to add those entries to the built-in dictionaries
[11:44] <cscott> i don't think the "transcluding a page with defs" is actually necessarily bad, so long as those defs would get scoped to the entire page
[11:44] <liangent> otherwise it creates unneeded conversion
[11:44] <cscott> liangent: is unneeded conversion purely a performance problem?
[11:45] <liangent> I should say excessive conversion
[11:45] <cscott> or are there words with multiple uses/meanings where the language converter would be overaggressive if a rule was in global scope
[11:45] <liangent> the latter
[11:46] <cscott> representing the sum of all the world's knowledge, in all the world's languages, is not an easy task.
[11:46] <gwicke> some way to specify a subject-specific dictionary could be added to the head too
[11:46] <liangent> gwicke: there was an attempt in core, with a parser function {{GROUPCONVERT: }}
[11:46] <liangent> but it hasn't been done
[11:46] <gwicke> templates are the wrong tool for that
[11:46] <liangent> and removed finally
[11:47] <cscott> for simplicity, i really like "all defs at head".  that reasonably generalizes to including subject-specific dictionaries.  but it doesn't handle the "defs scoped to a particular template" case.
[11:47] <gwicke> at least from our point of view, which is very much geared to independent reprocessing and template expansion
[11:48] <gwicke> defs scoped to a template could be fine
[11:48] <cscott> allowing defs to be block scoped handles the template case, but transcluded pages might still prove problematic (unless the transcluded page didn't create its own scope)
[11:48] <gwicke> but defs leaking out of a template is a no-go for our processing model
[11:49] <liangent> and what's the difference between templates and transcluded pages?
[11:49] <gwicke> same thing
[11:49] <cscott> liangent: defs leaking out
[11:49] <gwicke> cscott: there is no difference between pages and templates
[11:49] <gwicke> different namespaces, that's all
[11:50] <cscott> i'm referring to the use case, not the implementation
[11:50] <liangent> gwicke: no we store dictionaries in Template namespace too...
[11:50] <cscott> use case of transcluded pages is explicitly to allow the defs to leak out
[11:50] <cscott> use case of templates usually (we hope) doesn't let the defs leak
[11:50] <gwicke> cscott: templates are parsed in their own global context
[11:51] <-- jeff_evans has left this server (Remote host closed the connection).
[11:51] <subbu> ok, lunch time
[11:51] <gwicke> so global defs in there are fine (but would need work in the PHP preprocessor), and would not leak out of the template expansion
[11:51] *** subbu is now known as subbu|lunch.
[11:51] <cscott> gwicke: right.  but we'd break the pages transcluded just for their defs.
[11:51] <gwicke> transcluded pages are not supported
[11:52] <liangent> also you may want to think of the performance
[11:52] <gwicke> we have some plan on how to still support unbalanced templates combining to a single dom structure
[11:52] <liangent> there was really some tradeoff in the converter design
[11:53] <gwicke> by wrapping them in an extension-like tag
[11:53] <liangent> for example, the choice of using a global dictionary
[11:53] <cscott> my suggestion would be to provide another means to "include an extra dict", make the defs page-scoped, and explicitly add {literal} escapes for compatibility where needed.
[11:53] <liangent> ZhConversion.php has 19k lines
[11:53] <gwicke> cscott: yes, that is my preference too
[11:54] <gwicke> defs in templates would need to combine somehow for a given top-level template expansion
[11:55] <cscott> VE would then not directly expose the A/H/- flags, it would just add conversion dictionary support to that lovely page-level options dialog we saw in the wednesday meeting.
[11:55] <gwicke> yes, plus add the option to disable conversion or add manual conversion pairs locally without introducing rules
[11:55] <cscott> with a way to both add individual unidirectional/bidirectional mappings, and also an equivalent to "transclude this page of defs"
[11:56] <cscott> right, the non-flagged versions of the syntax are fine
[11:56] <gwicke> liangent: are templates depending on inheriting the page translation context too?
[11:57] <cscott> you mean, do changes in the page mappings affect included templates?
[11:58] <liangent> gwicke: it inherits currently
[11:58] <cscott> is that feature widely used?
[11:58] <cscott> gwicke: it shouldn't really be much of a problem; changing the page-level meta-options will likely force a re-render of the entire page regardless
[11:59] <cscott> oh, but then we'd have to track more dependencies between the template and the page context
[11:59] <liangent> depends on the type of the template -- for example, we may want it for infoboxes, or some inline-meta-templates, like {{main}}, but not navboxes (it's even sometimes harmful to inherit in this case)
[12:00] <cscott> a simple thing would be to have a single "uses conversion" flag that we'd set if rendering the template depended on the page context in any way during a full render
[12:00] <cscott> if "uses conversion" is false, then we can substitute updated template content into the page easily
[12:01] <cscott> if "uses conversion" is true, then we need to do a full rerender of the page when the template changes
[12:01] <cscott> one hopes that "uses conversion" is usually false.  if it's not, then we can implement more fine-grained dependency tracking.
[12:01] <liangent> cscott: actually we have some complex transclusion chain when using those dictionary-templates
[12:02] --> andre__ has joined this channel (~andre@***).
[12:02] <-- andre__ has left this server (Changing host).
[12:02] --> andre__ has joined this channel (~andre@wikimedia/aklapper).
[12:02] <liangent> if I have to add it to every level (like {{useconv:Template:something}}), that's somehow problematic
[12:02] <cscott> liangent: no, this is something parsoid's storage backend would internally track
[12:03] <cscott> part of knowing when to invalidate a stored article representation / reparse its templates.
[12:03] <liangent> then how can I specify that for specific template calls?
[12:03] <gwicke> could the translation context be category-based?
[12:04] <gwicke> (problem then would be that categories don't necessarily transfer across wikis)
[12:04] <cscott> ah, right, because the current inheritance behavior is sometimes-wanted and sometimes-a-problem.
[12:04] <cscott> gwicke: more magic words (sigh)
[12:04] <gwicke> no, I mean standard page categories
[12:05] <gwicke> [[Category:Sports]]
[12:05] <cscott> and i was saying you could add magic words to indicate which categories should get which behavior
[12:05] <cscott> customized per-wiki with the existing magic words mechanism
[12:06] <cscott> but maybe there are too many categories to consider doing that
[12:06] <gwicke> well, a translation namespace with pages corresponding to category names maybe?
[12:06] <gwicke> or define translations directly in the category meta info
[12:06] <gwicke> categories already have inheritance
[12:07] <liangent> gwicke: not necessary all articles transcluding the sports dictionary are directly in the Sports category
[12:07] <liangent> what if it has [[Category:Tennis coach]] ?
[12:08] <cscott> i would think you'd want something more like [[Dictionary:Tennis]]
[12:08] <gwicke> normally that category is directly or indirectly in sports
[12:08] <cscott> rather than overloading the category
[12:08] <liangent> cscott: that's just our previous GROUPCONVERT idea
[12:08] <liangent> and it keeps popping up from time to time
[12:09] <-- andre__ has left this server (Quit: andre__).
[12:09] <cscott> well, except using something other than the template mechanism as an implementation
[12:09] <cscott> but i basically like the GROUPCONVERT idea
[12:09] <liangent> also with it we can provide a better dictionary editing interface
[12:09] <liangent> with ContentHandler
[12:09] <gwicke> liangent: is the problem with directly using categories multiple inheritance?
[12:10] <liangent> if you want to have a look of what it looks like currently -
[12:10] <cscott> ok, i'm going to step away from the keyboard for a bit to walk the dog
[12:12] <cscott> liangent: that example you posted -- am i seeing nested dictionaries there?  ie, the IT dictionary includes the Games, Windows, Electronics, and Communications dictionaries?
[12:12] <liangent> gwicke: maybe - but will this allow people to attack the server
[12:13] <gwicke> liangent: depends on how the translation info is protected I guess
[12:13] <gwicke> could be restricted
[12:13] <liangent> gwicke: I mean, what if someone changes *this setting* on a very-top-level category?
[12:14] <liangent> cscott: no they're plain links. but there're some nested dictionaries. let me find one
[12:14] <gwicke> about the same thing as changing a dictionary template that is transcluded everywhere
[12:15] <gwicke> nested dictionaries are a bit like inheritance in categories
[12:15] <gwicke> complete with multiple inheritance
[12:15] <gwicke> would need a good rule on how to handle duplicate / conflicting rules
[12:16] [Notify] brion went offline (
[12:16] <gwicke> anyway, I think this is post-July stuff
[12:17] <liangent> cscott: I can't find it now but I've seen one
[12:17] <gwicke> liangent: Alolita is also very interested in this- maybe she could even organize some funding for work on this
[12:17] <liangent> it's just a Template:CGroup/* with some {{CGroup/**}}s in it