On Sat, 25 Jun 2016 09:57:57 -0500 Dale <rdalek1...@gmail.com> wrote:
> Neil Bothwick wrote: > > On Fri, 24 Jun 2016 18:47:11 -0500, Dale wrote: > > > >> I read the news item and was confused. I read it again and was > >> even more confused. After the third time, I didn't see any point > >> in reading it again so I went to the link, hoping it would be > >> better. Well, not really. So, I just started messing with it > >> until I got a setting that worked. Hey, it's in there and it > >> works. Now the news item and the howto don't matter. lol > > The point of the news item is not to make it work now, it already > > does. The advice is there to help you get your system into a state > > where it won't stop working when the next stage of the switch > > occurs. > > I get that but that didn't make much sense either. I ended up using > trial and error to get the setting correct since the news item and the > link wasn't much help. About all it did was let me know that there > was a change but as to helping understand that change, not much help > there if any. The news item says, If you have set LINGUAS in your make.conf, you most likely want to add its entries also to L10N. Note that while the common two letter language codes (like "de" or "fr") are identical, more complex entries have a different syntax because L10N now uses IETF language tags. (For example, "pt_BR" becomes "pt-BR" and "sr@latin" becomes "sr-Latn".) I can't tell from your posts what make.conf changes you actually made, if any. If you still need to make changes -- some packages are already using L10N now -- focus just on that one bit of the allegedly unclear news item and if it really is confusing ask about just that bit.
