05:30:24 <vishalvvr> #startmeeting i18n
05:30:24 <zodbot> Meeting started Tue Nov  3 05:30:24 2020 UTC.
05:30:24 <zodbot> This meeting is logged and archived in a public location.
05:30:24 <zodbot> The chair is vishalvvr. Information about MeetBot at http://wiki.debian.org/MeetBot.
05:30:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
05:30:24 <zodbot> The meeting name has been set to 'i18n'
05:30:34 <pravins> hi all :)
05:30:36 <vishalvvr> #meetingname i18n
05:30:36 <zodbot> The meeting name has been set to 'i18n'
05:30:43 <vishalvvr> #topic agenda and roll call
05:31:04 <vishalvvr> #link https://fedoraproject.org/wiki/I18N/Meetings/2020-11-03
05:31:09 <petersen> hello
05:31:24 <paragan> Hi
05:31:36 <epico> hi
05:31:46 <vishalvvr> #chair pravins petersen paragan epico
05:31:46 <zodbot> Current chairs: epico paragan petersen pravins vishalvvr
05:32:55 <vishalvvr> First of all, Thank you everyone for all your contribution and successful release of fedora 33.
05:33:16 <petersen> Yes it seems a good release indeed
05:33:46 <vishalvvr> Yes my upgrade went smooth without any issues :)
05:33:50 <paragan> yeah thanks all for your efforts
05:34:25 <pravins> +1, well done !!
05:34:59 <vishalvvr> Okay then lets start with today's meeting.
05:35:03 <vishalvvr> #topic Upcoming schedule
05:35:08 <mfabian_> ☺
05:35:18 <vishalvvr> #chair mfabian_
05:35:18 <zodbot> Current chairs: epico mfabian_ paragan petersen pravins vishalvvr
05:35:24 <vishalvvr> #info 2020-12-16 Change Checkpoint: Proposal submission deadline (Changes requiring infrastructure changes)
05:35:32 <vishalvvr> #info 2020-12-29 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
05:35:45 <vishalvvr> #info 2020-12-29 Change Checkpoint: Proposal submission deadline (System Wide Changes)
05:35:53 <vishalvvr> #info 2021-01-19 Change Checkpoint: Proposal submission deadline (Self Contained Changes)
05:35:55 <suanand> hi..
05:36:05 <vishalvvr> #chair suanand
05:36:05 <zodbot> Current chairs: epico mfabian_ paragan petersen pravins suanand vishalvvr
05:36:08 <vishalvvr> #link https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
05:37:22 <vishalvvr> anyone has any upcoming schedule to be mentioned?
05:37:50 <petersen> December not far away
05:38:13 <vishalvvr> true :)
05:38:47 <vishalvvr> okay then moving to next agenda item
05:38:55 <vishalvvr> #topic issues
05:39:04 <vishalvvr> #info #125: fix/backport xorg-x11-font-utils fonttosfnt for OpenType Bitmap fixes
05:39:10 <vishalvvr> #link https://pagure.io/i18n/issue/125
05:39:45 <vishalvvr> do we have any update on this ticket?
05:40:00 <epico> I think the upstream is still reviewing some other merge requests, will ping the upstream later.
05:40:20 <epico> two merge requests already merged.
05:40:30 <epico> https://gitlab.freedesktop.org/xorg/app/fonttosfnt/-/merge_requests/11
05:40:58 <epico> This merge request seems also improve the conversion.
05:42:05 <vishalvvr> Okay
05:42:16 <vishalvvr> Thanks epico for the update
05:42:25 <vishalvvr> Anything else to be discussed in this ticket
05:42:27 <epico> I think upstream will release next fonttosfnt for Fedora 34.
05:42:45 <epico> anyway I will ping upstream later.
05:43:12 <priyam> Hi
05:43:20 <vishalvvr> #chair priyam
05:43:20 <zodbot> Current chairs: epico mfabian_ paragan petersen pravins priyam suanand vishalvvr
05:44:10 <vishalvvr> Thanks epico, moving onto next ticket
05:44:12 <petersen> Thanks, I put a comment in pagure
05:44:38 <epico> Thanks, I will comment it too. :)
05:44:54 <petersen> epico++
05:44:54 <zodbot> petersen: Karma for pwu changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:45:12 <vishalvvr> Thanks petersen for updating the ticket i was about to mention that :)
05:45:40 <petersen> :)
05:45:41 <vishalvvr> okay then moving on.
05:45:44 <vishalvvr> #info #120: Fedora 31 Bug triaging
05:45:51 <vishalvvr> #link https://pagure.io/i18n/issue/120
05:46:29 <vishalvvr> any update on f31  Bug triaging ticket priyam ?
05:46:58 <priyam> total 4 bugs remained for triage
05:47:07 <priyam> working on them
05:47:31 <petersen> Bugzilla does not seem happy today
05:47:54 <priyam> yeah error while loading the page :(
05:48:32 <petersen> Fedora 31 EOL auto closure 	Tue 2020-11-24
05:48:46 <petersen> Anyway still 3 weeks, seems we are in a pretty good shape
05:49:19 <pravins> yeah, thanks to priyam  👍
05:49:38 <petersen> +2
05:50:09 <petersen> 1 became 2 !
05:50:46 <pravins> priyam: let us know, if for any particular bug you have any issues while triaging.
05:51:00 <petersen> Does someone want to add a comment for the current status?
05:51:21 <pravins> do you mean in ticket?
05:51:21 <vishalvvr> Thank you priyam for the update, may be good if you can update the count/status in the ticket
05:51:22 <priyam> yes.sure
05:52:35 <vishalvvr> Okay lets move on to the next ticket
05:52:40 <vishalvvr> #info #124: need for a generic fonts component in Fedora bugzilla
05:52:45 <vishalvvr> #link https://pagure.io/i18n/issue/124
05:53:10 <petersen> Okay
05:53:29 <petersen> Basically it is done - do we have any more tickets to add to the new component?
05:53:53 <petersen> But I would like to keep it open until next time, since tagoh is away today
05:54:21 <petersen> I thought someone should send an announcement mail to the fonts-sig
05:54:36 <petersen> (though we should probably have done that before also hmm)
05:55:26 <petersen> That someone can also be me, but let's wait for next time, unless someone wants to do it now?
05:56:27 <petersen> s/tickets/bugs/?
05:56:54 <petersen> Any comments?
05:57:55 <vishalvvr> yes, i do feel that it would be good if we can announce it on fonts list
05:58:25 <vishalvvr> I will take that as an action item.
05:59:12 <petersen> Alright we can work on it together then
05:59:29 <vishalvvr> Sure, Thanks :)
05:59:30 <petersen> I think it is important that it is announced the right way :-)
05:59:59 <vishalvvr> Anything else to be discussed in this ticket
06:00:00 <petersen> Since I pushed for it probably makes sense that I am involved
06:00:22 <petersen> then I can also get flamed if people object, lol
06:00:32 <paragan> good to announce it on mailing lists
06:00:40 <petersen> devel list too?
06:00:46 <petersen> Also i18n list
06:00:47 <paragan> not needed
06:00:49 <petersen> okay
06:00:55 <paragan> i18n and fonts
06:01:05 <vishalvvr> paragan +1
06:01:13 <petersen> Alright, that is a good start I think
06:01:26 <petersen> Though devel might make sense too perhaps
06:01:47 <petersen> See how the fonts sig reacts first
06:01:54 <paragan> Sure
06:03:17 <vishalvvr> If nothing more to discuss then lets move onto the next ticket.
06:03:24 <vishalvvr> #info nuspell package dictionary not found issue
06:03:32 <vishalvvr> #link https://bugzilla.redhat.com/show_bug.cgi?id=1892402
06:04:00 <vishalvvr> since bugzilla is down, so i have pasted the bug report in etherpad
06:04:08 <vishalvvr> #link https://etherpad.opendev.org/p/fedorai18n_03-11-2020
06:05:04 <vishalvvr> so in fedora Nuspell package looks for dictionaries in /usr/share/hunspell/, but they're actually in /usr/share/myspell/.
06:05:30 <petersen> hmm
06:05:41 <vishalvvr> but in ubuntu they have sym links for dict in hunspell dir, so it works fine over there
06:06:29 <petersen> Ubuntu uses myspell/ too?
06:06:35 <vishalvvr> yes
06:06:42 <petersen> Hmm I seee
06:07:07 <petersen> My first reaction was why not move the dictionaries to hunspell/ - it's 2020
06:07:15 <petersen> But I am no spelling expert
06:07:37 <petersen> But sure adding a symlink is easy
06:07:56 <petersen> does hunspell look in hunspell/ ?
06:08:28 <vishalvvr> petersen, sorry i dint get your question
06:08:28 <paragan> right can upstream be asked to have nuspell look into hunspell path
06:08:43 <petersen> You mean myspell??
06:08:51 <petersen> It already does iiuc
06:09:01 <paragan> sorry typo
06:09:21 <paragan> yes look into myspell path
06:09:27 <petersen> Or you can patch nuspell of course, but seems ugly
06:09:45 <epico> maybe good to add another path for dictionary searching?
06:10:05 <petersen> I would rather move the dictionaries - is there a strong reason to keep them in myspell or than history?
06:10:19 <petersen> * other than history
06:10:59 <petersen> But yes I think we have covered the solution space....
06:11:14 <petersen> vishalvvr: what are your thoughts?
06:12:02 <petersen> If hunspell uses hunspell/ then maybe it should really own the symlink I think
06:12:26 <vishalvvr> upstream seems to be very active for this project
06:12:26 <vishalvvr> so will try to report this in upstream
06:13:04 <petersen> Good idea
06:13:08 <vishalvvr> sym link seems to be easy fix for this though form our end
06:14:10 <petersen> either nuspell can or hunspell, seems currently nothing owns /usr/share/hunspell
06:15:06 <petersen> But hunspell owns myspell/
06:15:26 <petersen> .whoowns hunspell
06:15:27 <zodbot> petersen: owner: caolanm; commit: alexl, caillon, mbarnes, rhughes, rstrode, ssp
06:16:45 <petersen> Personally my naive feeling is that the dictionaries should be moved to hunspell/ and a symlink myspell -> hunspell added, but maybe that will break things dunno, shrug
06:17:03 <vishalvvr> maybe changing dicts from myspell to hunspell might break other packages
06:17:11 <petersen> But that is a distro decision of course
06:17:38 <petersen> Symlink ought to work, but who knows for sure
06:17:47 <vishalvvr> suggestion form epico was also good, if it is possible to add another path for dictionary searching
06:18:55 <epico> vishalvvr++
06:18:55 <zodbot> epico: Karma for vishalvvr changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:18:57 <petersen> Other problem with symlinking is that potentially it can lead to duplication if both paths are searched
06:19:37 <vishalvvr> petersen, right
06:20:34 <petersen> Anyway if the symlink works in ubuntu should be okay...
06:20:48 <petersen> unless they did more
06:21:27 <vishalvvr> okay let me report this bug in upstream and see what do they think/suggest
06:21:52 <petersen> Anyway clearly the nuspell upstream does not assume one should use myspell...
06:22:10 <petersen> +1
06:22:22 <petersen> Good to ask there first
06:23:02 <epico> +1
06:23:09 <vishalvvr> Okay, anything else to be discussed in this issue ?
06:23:59 <mfabian_> Is there a python module like there is for hunspell (python3-enchant)
06:24:18 <paragan> I think upstream does it supports it via "DICPATH" variable
06:24:53 <paragan> but i am not sure how to run or use it
06:25:15 <vishalvvr> mfabian_, nope they don't
06:26:16 <vishalvvr> paragan, i see
06:26:32 <vishalvvr> i am not sure
06:28:14 <vishalvvr> okay then moving to next agenda item
06:28:26 <vishalvvr> #topic Open Floor
06:28:45 <suanand> petersen++ epico++ vishalvvr++
06:28:45 <zodbot> suanand: Karma for petersen changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:28:48 <zodbot> suanand: Karma for pwu changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:28:51 <zodbot> suanand: Karma for vishalvvr changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:29:07 <vishalvvr> i have one topic related to liberation-fonts
06:29:18 <vishalvvr> #info Submit the fonts to Google Fonts
06:29:24 <vishalvvr> #link https://github.com/liberationfonts/liberation-fonts/issues/34
06:30:03 <vishalvvr> any suggestion/feedback on this?
06:31:43 <petersen> I think it could be done - on the other hand Google also has a similar font I believe
06:31:53 <petersen> How is the process?
06:32:07 <vishalvvr> petersen, https://github.com/google/fonts/blob/master/CONTRIBUTING.md
06:33:00 <petersen> Hmm OFL?
06:33:11 <vishalvvr> Yes
06:33:43 <petersen> Ah yeah so we are
06:35:05 <vishalvvr> earlier we had some request to ship liberation-fonts in otf and web formats
06:35:09 <vishalvvr> #link https://github.com/liberationfonts/liberation-fonts/issues/31
06:35:51 <vishalvvr> maybe lets start with that and gradually will think of adding it to google fonts aswell
06:36:58 <paragan> okay
06:38:05 <petersen> Sure, I don't see a problem with adding to google/fonts
06:38:15 <petersen> RFN?
06:40:10 <vishalvvr> did you mean RFE ?
06:41:57 <petersen> Reserved Font Name
06:42:26 <petersen> Anyways sure we can discuss more later
06:42:35 <vishalvvr> sure
06:42:45 <vishalvvr> thanks for you input paragan petersen
06:42:54 <vishalvvr> s/you/your
06:43:42 <vishalvvr> Let's close to meeting if nothing more to discuss
06:43:48 <vishalvvr> s/to/the
06:44:18 <vishalvvr> Thank you all for joining this meeting
06:44:26 <vishalvvr> #endmeeting