Handling of links as entities: A topic for discussion - Ubiquity i18n

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Handling of links as entities: A topic for discussion
Received-SPF: pass (google.com: domain of unatten...@gmail.com designates 209.85.219.222 as permitted sender) client-ip=209.85.219.222;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=BayUCUnITwifXGFiuophKlDE9gZyJMHY7bTfLRjvePg2KgbmUvpsHKX+G5bcEcrQWG
         iptcQzXtnCXAQMfuAWPmcXNbKUo3YBL+focg4zRUsHdCkqb6JIdP1ArdvVqe1AH/X8hy
         hm+MpmhgfBDDQ4RZwzIXyYRwOICaFliqw23LM=
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <AC92E5A2-4765-4783-AC65-1D924372E...@mitcho.com>
References: <1233a1c30908212055m1cda42an73dff9b716190...@mail.gmail.com>
	 <b004a98f-de40-40cb-913b-597b2cde7...@s15g2000yqs.googlegroups.com>
	 <1233a1c30908220808p2974bf83ub04c0c3ccb572...@mail.gmail.com>
	 <AC92E5A2-4765-4783-AC65-1D924372E...@mitcho.com>
Date: Sun, 23 Aug 2009 16:56:33 -0500
Message-ID: <1233a1c30908231456k16b8a920j8fe717432114...@mail.gmail.com>
Subject: Re: [ubiq i18n] Re: Handling of links as entities: A topic for 
	discussion
From: Lech <unatten...@gmail.com>
To: ubiquity-i18n@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

On Sun, Aug 23, 2009 at 3:48 PM, "mitcho (Michael =E8=8A=B3=E8=B2=B4
Erlewine)"<mit...@mitcho.com> wrote:
>
> 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
>
>>
>> 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
>>
>> On Sat, Aug 22, 2009 at 7:28 AM, Goofy<goof...@gmail.com> wrote:
>>>
>>>
>>>
>>> On Aug 22, 5:55 am, Lech <unatten...@gmail.com> wrote:
>>>> 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=3D5459&st=3D20#ent=
ry5
>>>> ...
>>>>
>>> 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. =C2=A0Thanks so much for your concern.
>>>
>>>
>>> - Goofy
>>> BabelZilla Team
>>>>
>>>
>>
>> >
>
> --
> mitcho (Michael =E8=8A=B3=E8=B2=B4 Erlewine)
> mit...@mitcho.com
> http://mitcho.com/
> linguist, coder, teacher
>
>
> >
>
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
