Quoting Karolina Kalic (karolina@resenje.org): > Hi, > > I'm guessing that work for ijekavian is done and we are ready to Indeed, it's not done as the locale is not in the glibc..:-) Still, what's left now is only sending the bug report with the new locale, then convert the new locale to latin and send another bug report to request the addition of sr_BA@ijakavianlatin. > * Zlatan should send bugs for translations that he has done again, > renaming them to sr@ijekavian and sr@ijekavianlatin. > * All those translations should be checked and reversed to ekavian. > Than we should reply to those bugs or reopen them if needed. I'd suggest cloning the original bug report, convert the renamed sr@ijekavian.po file to sr.po, attach it to the cloned bug report and rename that bug report to "Serbian (ekavian) translation for <foo>" > * We should write some documentation about how Serbian language is > translated, everything that we agreed about. Christian, where is this > kind of documentation held in Debian? Web site: http://www.debian.org/international/ Needs adding a "Serbian" entry there and add pages under http://www.debian.org/international/Serbian I'd also suggest that this list get notified when either an ekavian or ijekavian translation is made by someone so that it can be converted to the other flavour and committed|sent|whatever. In short, any translation work in one flavour triggers a derivative in the other flavour. This would be a very good example of efficiency improvement that would benefit other teams (Chinese Simplified vs Chinese Traditional or both Portuguese flavours, etc.)
Attachment:
signature.asc
Description: Digital signature