On Mon, 3 Dec 2012, Sebastian Andrzej Siewior wrote: > I think I can make iteven more complicated: Everything on the gadget > side uses language code 0x409 for en-us. The host-side on Linux takes > the first available language code and falls back to 0x409 if it (the > first reported) didn't work. > Now. Should we implement this or just stick to 0x409 by default. I > *seems* unused or lets say there is no strong requirement to use it. I > don't see a way on the host side to change the default language. > > If we decide to implement I could imagine > > strings/manufacturer.409 > > or even ditch the strings folder. However we could also add a langid > property and keep "manufacturer" (and every other string) in this > language id (0x409 by default). So "later" we could add other language > codes by creating manufacturer.401 for instance. The logical approach is to use a separate subdirectory for each language. Thus: strings/409/manufacturer strings/default could then be a symlink to the desired default language directory. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
