|
|
| Author |
Message |
< Ejabberd mailing list ~ Version 1.1.2: Minor translations update needed |
| Guest |
 Posted: Tue Sep 26, 2006 10:40 am |
 |
|
|
Guest
|
Op dinsdag 26 september 2006 12:10, schreef Mickael Remond:
<snip>
> > I also think the word "real" is confusing/duplicate; maybe 'Present
> > Jabber IDs of participants to'?
>
> All user are always seen as JID, but sometime you only see its JID as
> proxied by the MUC room.
> I think the work real make sense.
And what about 'Present Jabber IDs of participants' accounts to'.
--
Mvg, Sander Devrieze.
xmpp:sander@devrieze.dyndns.org
ejabberd, the expandable Jabber daemon. --
http://ejabberd.jabber.ru/
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Sep 26, 2006 3:54 pm |
|
|
|
Guest
|
On Tue, 26 Sep 2006, Mickael Remond wrote:
> Hello,
>
> * Sander Devrieze <s.devrieze@pandora.be> [2006-09-26 11:54:39 +0200]:
>
>> Yes, maybe, but tha might be more work as this will influence all
>> translations.
>
> Yes, this is more work but I will try to do it before the release.
> I think however, we need at some point to manage englis as a translation
> too, and use meaningfull but short code to represent message to
> translate in the source code.
> This will make it easier to change the English translation without
> impacting all other files.
While I agree with the sentiment behind wanting to use 'opaque'
identifiers in the code so that they don't need changing, it makes
casual reading of the code a little harder, since you need to more
carefully follow which error case/etc. you are in since you don't have
meaningful error messages anymore. Just something to keep in mind.
>>> I realize that I'm
>>> coming in to this late, but I really think the older text was better
>>> (though still not good) and that this late it is hard to make changes to
>>> strings (especially ones that have been being debated). If I had to come
>>> up with a new version of text for that option it would probably be
>>> something like 'Present real JIDs to', since they aren't discovered (at
>>> least not as in disco) and it isn't nearly as awkward.
>>
>> I also think the word "real" is confusing/duplicate; maybe 'Present
>> Jabber IDs of participants to'?
>
> All user are always seen as JID, but sometime you only see its JID as
> proxied by the MUC room.
> I think the work real make sense.
If we don't like 'real' (and that might be a good thing to avoid), and
we don't want to get into items as complicated as "Present Jabber IDs of
participants' accounts to" (which requires two or three layers of
indirect reference) we could go with something more like "Present (or
Show) participants' Account JIDs to", which removes the 'of' to make
things a little less reference-full while still getting the right sort
of sentiment.
Just another thought. I'm not wedded to any version of my text over
anybody else's I just think this is one of the harder options to explain
to people who don't already understand it and the text for it needs to
be a little more bullet-proof than most.
-Etan
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Sep 26, 2006 5:15 pm |
|
|
|
Guest
|
Op dinsdag 26 september 2006 17:53, schreef Etan Reisner:
> While I agree with the sentiment behind wanting to use 'opaque'
> identifiers in the code so that they don't need changing, it makes
> casual reading of the code a little harder, since you need to more
> carefully follow which error case/etc. you are in since you don't have
> meaningful error messages anymore. Just something to keep in mind.
That can be solved by adding a new feature to your IDE: showing the
translation instead of the identifier. The advantage is that the coder can
see the strings in his language and he can see immediately not so good
translations.
--
Mvg, Sander Devrieze.
xmpp:sander@devrieze.dyndns.org
ejabberd, the expandable Jabber daemon. --
http://ejabberd.jabber.ru/
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Sep 26, 2006 5:20 pm |
|
|
|
Guest
|
* Sander Devrieze <s.devrieze@pandora.be> [2006-09-26 19:13:57 +0200]:
> Op dinsdag 26 september 2006 17:53, schreef Etan Reisner:
> > While I agree with the sentiment behind wanting to use 'opaque'
> > identifiers in the code so that they don't need changing, it makes
> > casual reading of the code a little harder, since you need to more
> > carefully follow which error case/etc. you are in since you don't have
> > meaningful error messages anymore. Just something to keep in mind.
>
> That can be solved by adding a new feature to your IDE: showing the
> translation instead of the identifier. The advantage is that the coder can
> see the strings in his language and he can see immediately not so good
> translations.
And 'opaque' do not have to be that 'opaque'.
Something like: admin.login.required, admin.login.failed,
muc.room.jidshownto etc can give enough information to the developer.
--
Micka |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Sep 26, 2006 8:17 pm |
|
|
|
Guest
|
On Tue, 26 Sep 2006, Mickael Remond wrote:
> * Sander Devrieze <s.devrieze@pandora.be> [2006-09-26 19:13:57 +0200]:
>
>> Op dinsdag 26 september 2006 17:53, schreef Etan Reisner:
>>> While I agree with the sentiment behind wanting to use 'opaque'
>>> identifiers in the code so that they don't need changing, it makes
>>> casual reading of the code a little harder, since you need to more
>>> carefully follow which error case/etc. you are in since you don't have
>>> meaningful error messages anymore. Just something to keep in mind.
>>
>> That can be solved by adding a new feature to your IDE: showing the
>> translation instead of the identifier. The advantage is that the coder can
>> see the strings in his language and he can see immediately not so good
>> translations.
>
> And 'opaque' do not have to be that 'opaque'.
> Something like: admin.login.required, admin.login.failed,
> muc.room.jidshownto etc can give enough information to the developer.
Most certainly there are ways to make this not a problem, I just wanted
to make sure this 'issue' was thought about before-hand as opposed to
afterwards. I'm confident that things will work out fine in the end.
-Etan
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
