Handling of links as entities: A topic for discussion

2 views
Skip to first unread message

Lech

unread,
Aug 21, 2009, 11:55:48 PM8/21/09
to ubiqui...@googlegroups.com
I'm not sure how many of you here are also on BabelZilla, but I
figured for those who aren't it was worth getting some feedback on
this as it's something we've discussed while localizing Ubiquity.
Rather than simply performing a copy paste, I'll link you directly to
the discussion there and I'll attempt to answer any questions, or
entertain suggestions here. Hopefully I can get some feedback on this
idea, and how to possibly pull it off better if there's already a way
I've overlooked.

http://www.babelzilla.org/forum/index.php?showtopic=5459&st=20#entry51185

-L

Goofy

unread,
Aug 22, 2009, 8:28:06 AM8/22/09
to Ubiquity i18n
> http://www.babelzilla.org/forum/index.php?showtopic=5459&st=20#entry5...
>
I dropped an answer on babelzilla forum, with a minor suggestion I
tested unsuccessfully, hence i wonder if your own suggestion

<!ENTITY ubiqutiy.about.UsingParagraph1 "After taking the basic
tutorial on this page, you can learn more by reading the
&link.indepth;in-depth documentation page&acap;.">

will work on xhtml page. It seems to me tags and links are just
interpreted as text when nested in entities for xhtml.
But I am no coder, so it is quite possible you know some better way to
make it. Thanks so much for your concern.


- Goofy
BabelZilla Team

Lech

unread,
Aug 22, 2009, 11:08:04 AM8/22/09
to ubiqui...@googlegroups.com
Excellent, thanks for the feedback. I posted the link here as I wasn't
sure how much of the same people participate in both or just one or
the other. I just posted a quick follow-up solution which partially
solves the link just being printed out and turns it into a usable
link, it's not as elegant but seems to get the job done.

-L

"mitcho (Michael 芳貴 Erlewine)"

unread,
Aug 23, 2009, 4:48:20 PM8/23/09
to ubiqui...@googlegroups.com
Lech,

Thanks for looking into this problem. The direction of this discussion
is great: no longer splitting text up into the text before and after
links will be much more friendly towards various languages where the
word order is very different. The (less elegant, but working) solution
posted on the forums, Lech, looks good to me.

mitcho
--
mitcho (Michael 芳貴 Erlewine)
mit...@mitcho.com
http://mitcho.com/
linguist, coder, teacher

Lech

unread,
Aug 23, 2009, 5:56:33 PM8/23/09
to ubiqui...@googlegroups.com
I try :)

With the positive feedback from Goofy I've begun to refactor the DTDs
over the weekend using the known working method as I posted on which
appear to be quite flexible. I wasn't able to think of a better
solution so for now this works. This fix won't solve ever fragmented
entity, but should clean up most of the big ones, and when I'm done
the DTDs and about pages will have a noticeable entity reduction. On
the return, link management will also have been simplified since we
now have a pretty complete list of links found within these entities
and on the about pages. Necessary changes, additions or corrections
should be a breeze from now on even if things are a bit split.

-L

Lech

unread,
Aug 24, 2009, 2:30:08 AM8/24/09
to ubiqui...@googlegroups.com
OK, the refactoring is complete and looks pretty solid so far. I've
pushed the changes about an hour ago and it looks like I managed to
nail everything in one take. In the process I've also made a couple of
changes to some of the wording for a few entities which will require
translators to double check all keys which haven't appeared to change
but where the meaning may have. I'm not sure if we're pushing for a
pre5 just yet but I might recommend it, so I'm holding off on pushing
to BZ until later in the afternoon when everyone else is around.
Otherwise when we manage to cover the remaining error strings which
still require sorting.

-L
Reply all
Reply to author
Forward
0 new messages