 And what I propose initially to the organizer is an event, a daily event that we could schedule at some moment of the day and have the ITN and this all together. What I propose is first a very quick round table so that everybody knows who is everybody. So if you can please introduce yourself and just say a few words, what's your involvement in ITN and in a daily event or outside daily event, whatever you want. First start with Eddie. My name is Eddie Petriciola. I've been involved in the event for three years, which of those, all of them related to ITN, lately I have been doing other stuff. I've been involved in localization in Romania and recently I've started working on things like improving the ITN infrastructure. I've just created some firsts in the version of scripts which creates some companions for the translations for all languages and these kind of things. I'm just trying to make things better for, especially for us Armenians. We don't care about the others. Okay, so you won't speak anymore? Hi, I'm Cesar. I work for the regional government of Extremadura and I do localization in Spanish and I have been also organizing the game board sessions of Extremadura last year and we have also a server that we will maybe use in the future. We are always in Romania. Churro. And we are hosting it in Extremadura too. Hello, my name is Gephard, folks. People have known me as Arfi or more recently as Rhonda. I'm working on a German translation team or rather I've worked quite a lot. When I got involved in the deviant there wasn't really a team around. The website was mainly neglected and I translated quite a lot of stuff and did lots of stuff in that case. I also got involved a bit into upstream translation of some packages and we have a healthy team in the German translation part which works quite well so I took more or less a step back and it doesn't mean that I'm not interested in translation anymore. I'm just wanting to find a new spot for me in that area. Really? So rather liking to work on the nationalization issues more than on localization with translation work. My name is Leo Kaplan. I'm from Israel and I work on Hebrew support. I'm a member of the deviant Hebrew team and we work mainly on packaging Hebrew related stuff and not on translation. About a year ago I also started the deviant Arabic group to fix also their problems, especially packages like fonts and a-spell board lists and stuff which they didn't have. And there are a few other languages which ask to be on that group like Farsi or Iran and Kurdish and languages which are similar to Arabic and I hope to have a few other languages. I know you were then three reasons why I was here. The first one is because I sometimes, apart from my academic work, I collect news from for the debuts mixing and obviously the IATM and various different distributions are the main sources for my job. So I come here to do some networking and so if you have any job and you like to have some publicity for your work and I can put in the debuts mixing. And secondly, it's about my own interest because I was from Taiwan and I was using Xenian and now Wutu and the font and the different translation for the Taiwanese version of the debuts is very problematic because our, and sometimes it's even very political as well, it's not just technical things and so I'm here to hear about how these fonts and how our standards are made and how can we improve that and maybe report to my friends in Taiwan who unfortunately can't be here because of their job and various reasons. And the third reason is because of my academic job I do work to look at the development process and practically use their issues and requirement analysis and so I come here to do some fieldwork to understand how people discuss things and how actually participatory design and user-oriented design can be put together. Alright, so I'm Nicholas Feiger and I'm here because I've been working on the IE and Miele List for a little while I'm very interested in seeing how fonts can interact and serve the needs of internationalization and localization in the DAPN and other projects and I'm involved with the fonts team in EDIOT I'm a volunteer for SL International and we do things around fonts and input methods and writing systems I'm also a member of the OpenFont library and there will be a talk later on on OpenFonts and what's happening there and where we can go and where things can go and also we're really hoping we have a good collaboration with other teams so that more locales can be activated in the installer, that more translations can be done more than other locales. I'm Dr. Anugasi and I have a package that library called Crypt Graphite that will help our display and help the scripts of minority languages and I also help the general entrusts and I have them now. Philippe? Well I'm Philippe on IRC July 4 I've been involved in DAPN since 2002 especially with Translation 2004 from the coordinator of the Brazilian Portuguese Translator team and I've been part of the IATM admin team for the server that's extramodular delayed for us I'm also working on a little trine to merge DDP inside Poodle and other stuff inside Poodle and that's mainly with translations I'm Luciano and I'm just another deviant package Just another one Hi, I'm Cyril Bourgois a TV that would be easier I started working with Indians like translating and mostly reviewing translations for the French team but I didn't move to packaging and then games and we've spoken a bit with Savosva and Miriam Bourguis about problematic stuff in games like translation only available to images that are maybe unified or standard way to get translation in the Windows world where games author are developing their games and I'm looking for solutions for usable standard for Windows users maybe something different that gets text to a sensitive tool or something like that You're good too I'm Steve Longacheck I'm the guy who can't file a translation on his packages without him looking it over and trying to correct it for you My involvement with internationalization has been somewhat limited but I have some specific pet peeves that I want to try to take care of this week so I'm looking forward to working with people on those I'm Spanish I've been involved in local user group in Spanish I'm in the directive of three organizations like this In Debian I have been working for two years in a business managing software I'm Lik I'm a release manager now I've translated a lot of packages and web pages into Best I've sat back as translator I'm actually a more coordinated IATM effort in the release of Benin. I'm also a member of the admin team of the officer. Okay, and we do. The German guy and I start for some years the translation of the digital packages description. Now we have a new app in the city and I hope the running had different experience. And I hope also we can put all this stuff to put on. I think it's one thing that we should discuss in this week on that comment. I think it's not. So I'm Nicolas François or Nick Radon, IOC. I'm maintaining some internationalization related packages like Pau de Comfort PO4A and PUTL. And I'm also translating and reviewing translation for the French team. And you're currently dominating the world. Wow. Okay, thanks. Well, it was important I think to be sure that everybody knows each other. Yes. I'm Christian Perrier. How to pronounce it in English by the way. Just like Sam Osva also. So I'm not meant to be a DPR someday. Well, my main interest in Debian is obviously internationalization, localization because this is the only thing I can do. So this is why I'm in this stuff because as someone said a few, few hours ago, I have no programs and skills. I suck at administering machines. So the only thing I can do is take an English string and put it into French. Probably a whole program of 18 packages, isn't it? This is why I, for instance, maintain a lot of packages, not related at all with localization such as Samba, but I have some backup there. Well, my main point in all this stuff is to try to, as we say in French, to have all things work together and ask the world to come and go. If I can summarize last year's debcoff, we already had a few IT and sessions. The main conclusion was to decide to try building a common infrastructure. Everybody knows that Ubuntu has Rosetta. This is a quite good tool in these objectives. We all more or less agree that it has drawbacks when it comes to localization, especially around quality assurance and the like. So the idea was to build our own infrastructure in Delian instead of the various hacks we have all around together, material available for translators. One of the challenges we have is to make this material available for potentially new translators. Around this table, we are many, many skilled people. We can gather things from the SDN for whatever place it can be. That's okay for us, but if we want to extend this to more languages, more cultures, we need to make things simple. And that was the point, and we finally decided to go on with Putov because of the good support of the workforce people. And also because we can't go with Rosetta, because Rosetta is non-free. Since then we had this extramadural meeting thanks to Cesar and all the extramadural region people. And it gathered us, we did set up a server, so it's working now. And since then it did nothing. We did nothing with this tool. That's one of the challenges we have, is try to do something more with the server. At least with Putov. Actually the server does a lot of work that many people do not notice. The material now you find in the Italian website is available because of the script run on this server, because of the work of Tomahiro, who is not here currently, because of the work of Felipe and Nicolas, some little bit I did also. And we have to do more with this thing. Chris who mentioned the package description translation. This is a huge challenge, huge amount of translation. The current system doesn't scale very well with a load of work. So one of the challenges we have hopefully this week is to try to import the material in Putov and the like. There are technical challenges. So we have some technical sessions to help. Another challenge we have is to give our beloved release managers some good release goals for Lenny, for IATN of course. Nicolas sent this morning a mail to the Debian IATN mailing list which has supposed everybody around is supplied to. Well, the main point is to see if these release goals are acceptable for at least all of us and if we can think of other release goals around IATN. And of course any other topic that may come. The main point being here is to decide how we will do that. I propose a kind of daily work session. Would that be okay for everybody around? Of course we are like 20 people around but every other people are welcome and we could just sit down at some place. It would be hard to schedule because the schedule is already done so we may switch from time to time. But I would like to have it at the same hour daily. Does that fit with your schedule? Do we know an hour that works that doesn't put up with other talks? It's necessary conflicts somewhere. There is no space. Yesterday we rechecked during the order team meeting there is always more than one hour. Of course you know. Can you just pick a time then and obviously not everybody will make it every day. I think so. We should all do this during the lunch time. It's hard to do because people need to eat. How many hours are you thinking of? Two, three, four? Together? One hour I think is too short. Two would be good and then three hours you will be bored. I think we did lunch and then we did dinner. After the dinner it may be. I was thinking about 10 to 12. After dinner? During the evening. Usually we don't have talks, only boss. Usually after dinner we only have boss. So we could imagine using one of the talk rooms. Why not? I'm not with my notebook so I can check that. Possibly the low talk room looks very nice. Yeah, the lower one seems to be nicer than the upper one. I think easier for a small group. If somebody has asked us to check not on Penta but on GANF website. This is the P2 version. And there are two versions. Private one and official one. Should be everything on Penta but Penta sometimes doesn't answer as we would like. But as far as I see there is nothing after six in the various talk rooms. I thought the nights were pretty perfect. Yeah, there are boards, SPI meeting tomorrow. I don't know if it's possible but it would be great to know the topic of each day. Actually I have no topic. It's up to us to build a topic. We can set it up once now. That could be a good point. We are Sunday so we can say there could be an event tonight. Why not? Monday? Tuesday? Because we could have one. No, Thursday, Friday, Saturday. We can have at least seven. Thursday we can. Thursday is the season. It's the season. So no Thursday. So I think one Wednesday would be nice. And that would make six if we include Saturday. Yeah, a lot of people are leaving during Saturday afternoon. So at least five. Five of two are already quite good. Would it be okay for eight PM? Even earlier if we want. I have team meeting after organization seven. At seven? So eight would be good for you? Yeah. Eight is fine, so okay. Let's decide for eight. This is the final mark. I'm sorry? No. Oh, okay. Yeah, I can add this. I talked to Mark Heimers and I said to him we would schedule a daily meeting and I come back to him after this. So daily eight in the lower talk room. Everybody knows where the lower talk room is. You just go down. Follow the signs. Tonight there's already a meeting in the lower talk room. No, it's not in the lower. It's in the lower buff room. Am I right? Basement talk room. Basement talk for the SPI? Yes. I don't see it. This is your office. Maybe we can define a meeting place. Let's then try to find a place where we can talk together. SPI meeting is tomorrow. It's tomorrow but it's in the basement talk room. So we will move for tomorrow. We can do it in the lower buff. I'll see that with Mark Heimers. So eight starting tonight. We can do it tonight. Everybody was awakened. I think a schedule as the channel said would be good. So say, okay, tonight we will work on this, that etc. I think that would be make effective meetings because maybe I'm just interested in the technical part. I think it would be better to just more than just say, okay, come and sit down and we'll talk. We can do some extra material. Some schedule. With the same rules, laptops for a bit? Yes. No, I won't do it. You want your laptop. I want my laptop. The laptop is yours. Okay, laptop would be okay. It's up to you guys to use it on us. What would be good for tonight? Maybe first start on the release goals. I think this is probably what's expected by the release team. Michael also sent a message about release goal, right? What? Rizu sent one and Nicolas also sent one. It's basically the same release goals. Rizu sent about the package description stuff. Nicolas gave a few more ideas which are interesting to discuss. So that's good. I think would you be okay for tonight's release goals for ATN? Okay. My only wish for the next one could be put all the stuff at some moment. Yes, basically we have a lot of structure. We don't have much space, but we have space for room for people to do stuff over there. So one of the things that I'm going to do during this week on that phone is actually update the wiki of the ATN to have all the info. How we get an account, how we get access, what's available and stuff. And we want that wiki to not have duplicative documentation. It's just for administration purpose, just for info. The rest of the info should be on the Debian wiki. On the Debian wiki. The ATN doc on the Debian wiki. Churro admin on the Churro wiki. That's good. We could set a small summary for tomorrow for Monday. Just have you maybe do an overall presentation on what we have. Sure. Maybe Nicolas can talk about what is running. And Eddie also, your companion stuff on Churro. I will show the various things that we import currently on Inputor. Do you do the part of Thomas then? Do you talk about Thomas or do you want me to talk about Thomas? You probably know Thomas part better than me. And we keep space for a summary of what would be needed for importing Griswold's work. Yes. I still have the reports from Extremadura about how scary is importing the Debian wiki. Sorry. Well, just for everybody knows because almost nobody knows. We could only import one language for the whole DTP and Puto's top working. And we have like 27. It's much better now. Yeah. I think that Puto is much better now. Nicolas did an awful job with Puto's people. So I think what we could also decide is to force you to upgrade Puto. And package the last Puto's version. Yes. And upload it. And upload it. But I can't upload it. The version testing is newer than the version in Edge. The version in Glein. I don't think so. But the package for the new version is done. I'm just thinking about packaging the next one. Because it should come quite early. But Christian wants this one. I think we need something that's Puto 1.0.0. And it would be too bad to wait for Puto 1.0.1. Okay. It will be better than 1.0. Because I can just upload backports for you. The performances of Puto 1.0 should be checked. Yes. Okay. When should you check it? It wasn't tested on a server with 20,000 of Q5. We have one? Yes. We have one. So yeah, that could be the second part of the meeting. The IP addresses. Yeah, we can use one or two more. Maybe we can buy a bigger hardware too. So actually it would be good if we have the new Puto by tomorrow. Okay. But we don't have to wait for you to officially release the Puto package in the archive. You can just build one for Edge. It already exists. Okay. So you give it to Philippe? Yes. Just find an IRC and I will install it. Okay. So that gives us a kind of Puto session on Monday. Sure. I'm not sure we will be able to work on DDTP stuff at the same time. We need to save space for specific DDTP work. I don't know if there is much DDTP work. I think that we should have Grisoo going to use all of us with how the DDTP works for the... Our secret plans for the future is having an i18.dev.org which will be in Puto and the DDTP on that server. So that's one of the things that we have in mind. Like having our infrastructure over there. Yeah. So we have to switch all the translation and all the stuff to Puto. And shut down my old server. Okay. For this. Yeah. What we need to find is the bridge between the two ways to work with CUNC and DDTP. That's some teams already used. Yeah. They are using the DDTS. DDTSS. DDTSS. Yeah. DDTSS. And they use it well. They are now used to it. So we need to... There's more summary by you if you can. Just informal summary of how is the DDTP now? What it is doing? And what is the DDTSS and so on. And how do you produce PO files currently? And then we'll see how we can import the product. Yeah. That could be on Tuesday. Have we some byteboard or something like this? Some? Some byteboard. Two bytes. I write board and didn't install only screen. Only screens and projectors. But write board they didn't install. I would try to find a flip chart. A flip chart, yes. I'm not sure if we have time to do that. It's hard to explore. I must prepare some stuff. Wednesday, Wednesday is the tourist day. So do we plan something on that day? Will everybody come if we have a meeting at 8 p.m.? Okay. The place is open. Nobody. We can use the place. I would be there. Anyway it will rain. You don't have to go outside. It's a boring city. I think maybe most people will come back to have the sponsorship. Yeah, I think so. So I think that 8 should be okay. So okay. 8. Okay. What do we do? Well, we'll talk about churro, puthol, pptp. Release goals? Release goals already. Yeah. We need probably to save the last meetings for... Conclusions? Well, maybe conclusions or things we don't have. We didn't have time enough to discuss. One of the things that probably you should address, that is not address, should be addressed in the puthol, is the license again? License of... For translations. I mean, we will have the infrastructure. We don't have it, but we also didn't write like a couple of lines of policy to say that you should license your translations to be clear. It's not long, it's just a short guideline. I'm doing that in Brazilian Portuguese, but it's... Another thing that I would like to discuss, and I don't know if we have much room for that, is the website, because we're starting changing a few bits of it, and we start... We are preparing now... I didn't fund just it yet, but I will try to find it, because Dom is checking the licensing and I'm checking the WML structure, because we want to move it for a new website, for new face and all that, but without all the hype of mock-ups and publish. But I would like to hear with the translators how the WML is important, how we can change things without breaking everything. So, translation licensing websites, website documentation, does it fit together? Awesome. I think that Javier Fernandes is not here, but he will come probably at the next sessions and he would be interested if we have some discussion about documentation. Yeah, because we are using several types of documentation, like DevinDoc in some parts, DocbookXML in other parts, and probably... And sometimes it's translated with PO files, sometimes it isn't, so it's not very consistent with all of the Devin documentation projects, I think. So, that would be a lot for Wednesday. The website is just small, it's not... So the point is not really to present again what to do, I think we are more or less aware of these things, but to change ideas again. To try to find a way to... To find a way to... Realistic goals, because we all have big ideas and we never achieve all of them. Maybe some app maintenance on the Docbook. It should be here. Maybe we should take one session with app maintainers to discuss the goals that Nicolas had in the email because of the T-debs translation depth. I think that was a big goal and I think we should put together the translator and the release managers and the app maintainers to discuss the techniques and so... The things about T-debs. Let's call these T-debs or one, even if T-debs are not a good idea, I don't know, but because I remember the discussions between Eddie Javier and the extra Madura, we have a good summary. I went on it recently, you did what? And we have a good summary on the wiki about these T-debs with very good ideas and someone was talking... We had a talk yesterday with wiki and we kind of rethought the whole idea and the problem with T-debs is that it increases really, really in a very large scale the number of packages actually. As it is proposed now, it would actually create one supplemental package for every pair of packages. Actually for every package you have as many supplemental packages as translations. So that would be huge. And on the other hand, what I've talked with wiki was that maybe we should instead try to implement what Scott James Remland suggested a while back, I think three or four years ago when he talked about the PKG2 and creating some kind of classes of files within every DBM package. So you actually use some classification and you use some filters on those class of files. So on a default system, you would actually install everything as you would usually but if you want to have a custom thing then you would actually unfilter. So they actually say, okay, these are Romanian translations so I want all Romanian translations to install everything else, every other translation. This is basically the idea of Ubuntu localization packages. Am I wrong? I think you're also looking at this is creating the packages and then updating separately. This is the same idea of marking back with confi files inside then so it should be like removable files or something like that. Actually you have something like classified types of files. You have mumpages, you have documentation or abstract classes like this. Yeah, it could be used for more things than just localization. Yes, and that's why you can do all this slash doc stuff and slash dev stuff. You can make one library package, just have the whole library and to separate the documentation, separate the dev files, separate the translation files. This way we can work on the same infrastructure with the MDM people. So definitely we need a session for this, right? Yes. Okay, we're buying one. We are Friday. I'm not sure but maybe I think Wookie schedule something but I'm not sure when. Can you coordinate with Wookie to... I'm going to go there anyway. Yeah, but so that we don't collide or do the same thing in two different sessions. So okay, the responsible for this session is me. The one for the presentation. Can you translate with Michael Wacht? Yeah, we need to bring Michael Wacht. Michael with Michael? How do you pronounce Michael in German? Michel. Michel and not Michael Schumacher. No. Michel. Michel Schumacher. So Michel Wacht, we should bring him. Anyway, I think we'll be interested in most of the things, even if we say bad words about Rosetta in some places but... and say that Puto is better and like... Okay, so it would be nice to have someone feeling more in charge for each session so Eddie has been nominated for Friday about the debt and the right. No, maybe he doesn't volunteer. Yeah, I did. For Wednesday, Felipe is well-nominated. Yeah, everybody. Okay. After this meeting and you should send this notice to the listing. And... Your volunteer program. For the summary, I volunteer. Thank you. For writing long and stupid, boring mails, I always volunteer. Yeah, the Puto session could be... Who could manage the Puto session? Nicolas. Yeah, good idea. Nicolas is good. Okay, it's for the Puto session. And... The release goals... Luc, of course. And... Okay, we have release goals for Sunday, for Monday with Puto, everybody summarize what we already do on Puto. Sure, it's also Monday. And... a more technical session about how to report DTPSS how to report DTPSS to Puto, it could be on Tuesday. It's good, I think, to have it early, because afterwards we will want to work, to do technical work between probably Felipe, Grisou, Nicolas. I won't do any technical work. And you'll just crack me shells. Maybe some guys will review mine. We'll review mine. Okay, for that part that DTPSS stuff will nominate Grisou as responsible. Just move the things. Not the only one to speak. And we can save for the people who are still here on Saturday a kind of summary. Maybe we can scale it earlier. You should be in the morning. In the morning? Before people leave. Waving, I think. I'm waving. Okay. Fine. I'm living on Friday. You're living on Friday. It's like the flight was three hundred dollars more cheaper. Okay, you don't stack. Okay, so we're small on Saturday. If we can, it'll be good. When is to summarize? When is scheduled the presentation of Churro? Churro is on Monday. Churro is on Monday. Churro is on Monday. I wouldn't call it a presentation. Yes, presentation of the various services. What we are already doing on Churro is on Monday. Okay. Just before the cheese party. We have a collision here. Because the cheese party organizers are here. The cheese party is at ten on Monday. And of course, all internationalization people are deep cheese lovers. So, if you remember, I say Maduro. Yes. I'm wondering if they could clean the room that the cheese is. I think so. They demolished it. And I remember he was smiling. I put a picture after eating that cheese on my blog, so you can enjoy it every time you want. I'm going to review. Projects meet. Talking about something. Say a word about it. After all, it's all about English localization. So, we are able to discuss the NMU campaign. Ah, interesting. Do I have any statistics? Okay. I completely suck at keeping statistics or information. I just do the work and no idea. We have some small graphs. It's really the last week. Yeah, because Nikolas did set up something. But is it really right? Yeah, it's working. Yes, no, it's working every day. So, we will have the graphs. We only have the... I could be nice, yes. I appreciate it, yes. And this way, you could work to have a Brazilian Portuguese 100%. Oh, it's right. We are no longer 100%, I'm afraid. And thanks to the Smith Review Project, I think the statistics are lowering. Shall we talk about fonts or input methods? Yeah, yeah. Maybe the interaction with the two teams and what... I could be part of the release consequence. Yeah, the point is this font packaging team I launched it without knowing anything about fonts. It's working and we have now the... The road is slowly taken by Nikolas so I will rest and sleep. And yes, there are a lot of things to do about fonts done and interaction. I don't know if we have room to talk about that. I'm looking for... I think is there a policy on what translators are using? Let's say a new translator wants to use PUT or is there going to be a recommendation on a particular font to use or particular input methods? Is PUT itself going to have fallback for other fonts? I think... There may be something defined like that. I think the PUT guys are trying to gather some information about various languages, what is the preferred font, preferred size and other stuff. Is it possible to underline some text or just in some languages? If you underline the text just not readable, so you have to use another trick. Sometimes there are sizes and sometimes you need to have the browser also understand some languages. There are some rendering issues sometimes. So I'm pretty sure they are aware about the problem. I don't know how it is implemented in the PUT server because it's more the word for a guy who works on that. This is a bit at the office conference in Lyon but maybe there could be an item on the team's to-do list. Christian you showed me the page of the Wiki where there are lists of recommended fonts or fonts being used in the installer. Would it be useful to have a big poll among the translators asking for their input? I prefer this font because it was better for that and maybe have that in the same Wiki page I think that would be useful. And also for the font maintaining team to identify which fonts would be most usefully packaged or if there are fonts that are restricted then maybe contacting the upstream and saying okay it would be great and this kind of overlaps with the font choosing procedure in the devian installer for the graphical installer. The page Nikola and I were talking about is the page about who had fonts maintained by Davide and so we have to be careful about not overlapping but Davide is already involved in the package. So that I don't think it would overlap actually me being in the font is kind of an attempt to avoid forking efforts. So yeah there's a lot of things to do there has been a discussion recently on the package fonts about the various fonts for Chinese language and Chinese language because there are some complex issues I don't understand anything about this stuff. There are technical issues as well as legal and licensing issues but I think it would be useful to be able to identify where the work should happen. Maybe it's a different kind of use case maybe the fonts that you use that are best for the installer might not be the fonts that you use on your browser when the system is installed or the fonts that you use to create that's related to the installer because when you choose to install say in Japanese you want the best for Japanese so this is related to task set to localization tasks what to install everything. This installation with the two localization config does I think personally that localization config is dead the point of this package for those who don't know about it is was to two final steps of localization but it touches every package configuration file so by definition it's completely policy broken so it should be RC it should not be in testing and it is not if I'm we find RC bug at the end of H3 cycle about it it seems that the deviant edu people are still interested in it but I think after I maintain it for a while it's not necessarily the correct approach to configure other packages according to localization with better package to have GDM respect the local settings etc so I'm not sure it's related to localization no I thought because it goes to the full point it's closer to task set and distance finding the right font to incorporate even localization task is very very difficult especially complex languages not all complex languages actually from the translators and from the people in the communities that use these languages I think they are the best people to give us that kind of information because even the best designers won't know the right consistency or the way the script should appear you have to ask the people we know that's obvious but maybe setting up a project apparently on this issue the efforts are more or less joined with Ubuntu people on the Ubuntu side there's also a review going on here some of them joined font packaging recently we've launched a description about font the big mess of fonts in the beginning Ubuntu also the future of the format but it reminds me that Michael I had I had a script also to do font configuration especially for TGK languages so not exactly a look like config but we just touched the font configuration according to the account especially for font experts this is something I hear what you mentioned when you introduced yourself this is something we might need more input from the communities especially in the CK languages communities because the knowledge is somewhat rare actually I was just talking to people in Taiwan and it would be interesting to participate in your working sessions but it needs to be late for them 3am so if you're going to have these font and implement the working session maybe you can branch it in the morning midday that would be nice also for the people working on input methods in south asia and india all around the country so maybe you would like to work here on IRC or something in Extremadura we had Tabunaka who is one of the real specialists of input methods so we need to involve all these people the difficult part is to follow what is explaining because it's big fans really interesting but they do a tremendous job in this part and we need a lot of people involved in the old complex languages or VD stuff we discovered recently broken stuff in DI about VD you never noticed balsh reported by yeah that's also a challenge because I think the main challenge for all open source so called open source stuff is lies in Asia, in Africa complex the war is already lost in Europe anyways there are so many items in the stack different methods to run languages some things need to work together terms of languages oh this is the ethnologue you guys all know about the ethnologue website the bible for the people working on it okay someone comes with a strange language and you see you have the entries and statistics and some things I spend a whole day ethnologue there are projects also to kind of create the same database database of writing systems so this is for languages and where they're spoken what family they belong to and so on but with SL and people contributing and working on setting up the same for writing systems so you have an entry also like the font the recommended font for that language the recommended writing system also kind of a source forge for writing systems but it's still in the works I'll mention some of the work done in that area at the font site sometime to talk about SL specifically for SL it fits the Debian philosophy so you guys are all okay for IITLan sessions in the evenings and good and Nicolas will back it in two hours and we will have it on Churro I just checked this morning it was completely dead the put-on server was not working and no one noticed I just had to restart them the put-on server? the put-on server just connected on port 8080 you showed them you're the admin I'm the user so if you're interested I'll get some file files from it we should plan to have if that's possible an extra manual emitting again I think it would help us to advance again on all these things and maybe focus it on a specific program I think that advancing on put-on would be a good target and a very specific meeting with a few involved people in the night so we need to keep this in mind and to see with I hadn't mind to make it at the end of the year but did you happen to see your again? it's already... we talked about that if you're not aware we reported about the meetings we reported them in February the press conference so all the six meetings were presented in December it would be a good time to see what's the status of the release codes it fits the release schedule so targeting something in late November December or something would be good so we would keep time for this at least at the final meeting okay, you're free great thanks