Marcel Holtmann <[email protected]> writes: > Hi Kalle,
Hi Marcel, >> I translated my UI to finnish and noticed how awkward it is to show name >> "Wired" otherwise the application is using finnish everywhere. The >> problem here is that Wired is not the name of a network (contrary to >> wifi or cellular networks which have specific names), and it stands out >> in a really ugly way. >> >> So I think I should translate Wired somehow in my UI. But how should I >> do enable the translation? For example, if type is technology and name >> is "Wired" it should be translated? Or should I do it differently? > > I thought about this as well. One option was to leave the Name property > out for these networks and force the UI to look at the Type property. I prefer that there is a Name property like it is now. Makes it easier for simple command-line tools, for example. > In the end we can not have a total unaware UI that has no idea what the > different network types are. So yes, you need to look at the Type and if > it is ethernet then you should replace the name with something that can > be translated. Ok, I'll do it like this. I see problems with this aproach when you have two ethernet devices. But I don't worry that now, I want to first make everything work with just one ethernet device. > To some degree cable connections are just special. Even inside ConnMan > they have some special handling. It does auto-connect when you plug in a > cable, they only show up when plugged in etc. > > So far only cable connections are special and I think this is an > acceptable exception to the general rule. I agree. Thanks. -- Kalle Valo _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
