Supporting multiple languages in a single document

[Milian Wolff]

On Wednesday 16 June 2010 19:30:55 Niko Sams wrote:
> On Tue, Jun 15, 2010 at 17:11, David Nolden <zwabel at googlemail.com> wrote:
> > The big question is whether we should create one TopDUContext for each
> > contained language, or whether we should create separate top-contexts for
> > the languaged.
> 
> Would it be possible to have a single TopDUContext and a tree of contexts
> from mixed language contexts? That would be the most correct way to
> represent them i think.

Yeah, I second Niko here.

But I'm not sure how deep the changes in the DUChain would be to make that 
possible. But if we could "jump" into a different context/declaration builder 
and just pass it a range to handle, this would be awesome.

On the other hand I still want to do something like:

currentContext()->topContext()->findDeclaration("foo") <-- _only_ declarations 
of "foo" in the current language...

So I don't know how that should be handled when a top context has child 
contexts of different languages...

Otoh, as said, it would be cool to create uses for declarations in a different 
language, e.g. <htmlTag id="foo" /> and #css #foo {...}.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100616/f755f45a/attachment.sig>