Re: Summary/Minutes from yesterday's FESCo meeting (2018-08-20)

[pravin....@gmail.com]

On Thu, 23 Aug 2018 at 17:02, Kevin Kofler  wrote:

> Zbigniew Jędrzejewski-Szmek wrote:
> > #1957 F29 Change: Liberation Fonts 2
> > https://pagure.io/fesco/issue/1957
> > DECISION (+6, 0, 0)
>
> Sigh!
>
> Really nothing has changed since the decision in Fedora 19 to stick with
> Liberation 1, only 4 years have passed without any changes whatsoever to
> the
> "Liberation 2" fonts.
>
> Liberation 1 is no longer developed upstream, but as far as I can tell,
> neither is Liberation 2.
>

Agree not much happened in upstream. Its because i was busy in other
project and also conflict between Liberation 1  and 2. Basic idea behind
Liberation 2 was to stop bug fixing on Liberation 1 and develop 2 for
future.  But still we were using Liberation 1.
Now, we have new maintainer for Liberation Fonts and with clear direction
for Liberation 2, he will do the required bug-fixes and enhancements into
it. He is already working on adding BitCoin glyph to it.


>
> "Liberation 2" fonts are essentially rebranded Google Croscore fonts.


No, Liberation 2 are not just re-branded.  We have done bug-fixing and also
added Serbian language support into it. [1]

And
> those Google Croscore fonts are, in fact, already packaged in Fedora
> (https://src.fedoraproject.org/rpms/google-croscore-fonts). Why can't we
> just let Liberation be Liberation and Croscore be Croscore?
>

Unlike Liberation, Google just released .ttf version for there fonts. I
have not see any way, to fix issues in Noto upstream [2] and rebuilt that
.ttf.
In Liberation 2, we have source file .sfd, one can fix, provide patch.

Thanks Kevin for raising this point, i assure will get more development on
Liberation 2 soon. Bug list for Liberation 2 [3]

Thanks,
Pravin Satpute

1. https://github.com/liberationfonts/liberation-fonts/commits/master
2. https://github.com/googlei18n/noto-fonts/tree/master/hinted
3.
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=liberation-fonts_id=931=Fedora_format=advanced
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Liberation fonts plan

[pravin....@gmail.com]

On 20 June 2017 at 22:37, Matthew Miller <mat...@fedoraproject.org> wrote:

> On Tue, Jun 20, 2017 at 06:46:31PM +0530, pravin@gmail.com wrote:
> > > On Tue, Jun 20, 2017 at 06:35:24PM +0530, pravin@gmail.com wrote:
> > > >- In Fedora we will have both packages liberation2-fonts and
> > > >liberation-fonts
> > > Will the actual fonts have different names?
> > I am planning to have same fonts name, so one can simply install other
> > packages and replace the existing one.
>
> This seems likely to lead to user confusion. Any chance of making the
> old one "Liberation Classic" or something like that?
>

I liked the idea. With this case we can have both fonts installed same time
on the system.

Regards,
Pravin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Liberation fonts plan

[pravin....@gmail.com]

On 20 June 2017 at 18:42, Matthew Miller <mat...@fedoraproject.org> wrote:

> On Tue, Jun 20, 2017 at 06:35:24PM +0530, pravin@gmail.com wrote:
> >- In Fedora we will have both packages liberation2-fonts and
> >liberation-fonts
>
> Will the actual fonts have different names?
>

I am planning to have same fonts name, so one can simply install other
packages and replace the existing one.

-
Pravin


>
>
> --
> Matthew Miller
> <mat...@fedoraproject.org>
> Fedora Project Leader
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Liberation fonts plan

[pravin....@gmail.com]

Hi All,

   Presently as you know, we have liberation-2 and liberation 1.07.4. i am
maintaining both in single git repo. [1]

I am thinking to create different project for liberation2, reasons as
follows

   - liberation 2 - It initially forked from google-croscore-fonts and now
   independent development is happening.
   - liberation 1 - Though shapes are same, liberation 1 has bytecode
   hinting instruction, many users like it.
   - Problem: Few users want to use liberation 1 and few users want to use
   liberation 2.
   - Having different project for both will help for independant
   development and also users can switch as per interest.
   - One can obsolete to other.
   - In Fedora we will have both packages liberation2-fonts and
   liberation-fonts

 Let me know - feedback and suggestions.   Copr for liberation2 [2]

  Background information on Wiki. [3]

Thanks,
Pravin

1. https://pagure.io/liberation-fonts
2. https://copr.fedorainfracloud.org/coprs/pravins/liberation2
3. https://en.wikipedia.org/wiki/Liberation_fonts
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 Self Contained Change: Transdiff

[pravin....@gmail.com]

On 12 January 2017 at 14:33, Tom Hughes <t...@compton.nu> wrote:

> On 12/01/17 06:59, pravin@gmail.com wrote:
>
> On 10 January 2017 at 14:39, Tom Hughes <t...@compton.nu
>> <mailto:t...@compton.nu>> wrote:
>>
>> I don't really understand the logic here...
>>
>> I would expect anything in Fedora to be built with whatever
>> translations are provided in the upstream release - are you saying
>> that packagers are routinely removing such translations for some
>> reason? or just forgetting to package the extra translations?
>>
>> Yes, forgetting to pull translation is one of the problem.
>> Also other problem is packages updating strings after translation is
>> completed. This also result in loss of translation.
>>
>
> Right, but both of those are primarily issues for upstream rather than for
> Fedora packages.
>

Yes

>
> Or are you proposing that packagers should be pulling translations
>> from some additional source above and beyond what upstream provides?
>>
>> No, not this.
>>
>
> OK.
>
> I'm not saying we should package a tool for analysing translation
>> status as I'm sure it will be useful to upstream developers but it's
>> not clear how you envisage it fitting into the Fedora development
>> process.
>>
>> In Fedora development process, i think such a script/project will be
>> helpful like.
>> After Beta release, one can simply run this script on fully installed
>> translation machine and verify whether all latest translation from
>> upstream are available in Fedora or is there any specific string
>> breakage (i.e. New English words in package ).
>>
>
> Right, but as a Fedora packager if I have the latest upstream packaged and
> this script says I am missing translations what will I be expected to do
> about it?
>
> You've already said you don't expect packagers to patch in the extra
> strings so we can rule that out.
>
> So presumably I'm just supposed to open a bug with upstream to tell them
> and then hope they do a new release and that I can then get that in before
> GA?


Perfect. This is more from Translation team side. Since many time even
after 100% translation in Zanata, we do not get those in Fedora release.
Basically translators will report bugs for this.

-
Pravin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 Self Contained Change: Transdiff

[pravin....@gmail.com]

On 10 January 2017 at 16:31, Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:

> On Tuesday, 10 January 2017 at 09:39, Jan Kurik wrote:
> > = Proposed Self Contained Change: Transdiff =
> > https://fedoraproject.org/wiki/Changes/Transdiff
> >
> > Change owner(s):
> > *Sundeep Anand 
> >
> > Often even after 100% translation in Zanata, few packages do not get
> > build with latest translations in Fedora. This result in poor
> > localization experience. Transdiff is a python program to run on
> > products installations for tracking translations with project upstream
> > and generate diff reports.
>
> Nice. On the wiki page, you (Sundeep) also mention automation.
> Where do you see this in our packaging pipeline?
>
> As a taskotron check? A regular report mailed to the devel list?
>

Good point. While discussing on string breakage monitoring we discussed
this idea as well.
Yeah, taskotron is good fit for uses of transdiff, so rather than post
installation of translation, we will have this check in Bodhi itself.

-
Pravin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 Self Contained Change: Transdiff

[pravin....@gmail.com]

On 10 January 2017 at 14:39, Tom Hughes  wrote:

> On 10/01/17 08:39, Jan Kurik wrote:
>
> Often even after 100% translation in Zanata, few packages do not get
>> build with latest translations in Fedora. This result in poor
>> localization experience.
>>
>
> I don't really understand the logic here...
>
> I would expect anything in Fedora to be built with whatever translations
> are provided in the upstream release - are you saying that packagers are
> routinely removing such translations for some reason? or just forgetting to
> package the extra translations?
>

Yes, forgetting to pull translation is one of the problem.
Also other problem is packages updating strings after translation is
completed. This also result in loss of translation.


>
> Or are you proposing that packagers should be pulling translations from
> some additional source above and beyond what upstream provides?
>

No, not this.


>
> Zanata appears to be a web based translation platform that developers can
> use so I would expect the workflow for a package that uses Zanata to be
> that upstream pulls the latest translations from it at regular intervals
> and incorporates them in the releases they make which then get packaged in
> Fedora.
>
> I'm not saying we should package a tool for analysing translation status
> as I'm sure it will be useful to upstream developers but it's not clear how
> you envisage it fitting into the Fedora development process.
>

In Fedora development process, i think such a script/project will be
helpful like.
After Beta release, one can simply run this script on fully installed
translation machine and verify whether all latest translation from upstream
are available in Fedora or is there any specific string breakage (i.e. New
English words in package ).

At the present still exploring ideas, once we have basic script ready we
can further think how can we use it for more benefits to Fedora translation
quality.

-
Pravin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F25 Self Contained Change: IBus Emoji Typing

[pravin....@gmail.com]

On 11 July 2016 at 16:55, Bastien Nocera  wrote:

>
>
> - Original Message -
> > On 07/08/16 20:41, Bastien Nocera-san wrote:
> > > I think that the emoji input method should be a separate input method,
> so
> > > that most users would have the choice between inputting using the
> keyboard
> > > layout that matches their keyboard, and a separate input method for
> > > emojis.
> >
> > I think the emoji typing does not depend on XKB but is used frequently
> and I
> > don't think it should be separated.
>
> It is on every other platform I can think of.
>
> > If the engine should be enabled by default for any languages, I think it
> > would make sense that the XKB engines also enable emoji and switching
> > engines
> > would be more cost than switching input modes.
> > Once this feature is implemented, the translatable annotations also can
> be
> > implementable for input method engines.
> > I think other platforms does not separate engines for emoji typing.
>
> They do.
>
> > > The IBus XKB engine is not discoverable (it's not listed in GNOME's
> Region
> > > & Language settings) and the keyboard shortcut to input emojis is also
> not
> > > discoverable. Having a separate input method is likely the better way
> to
> > > implement this.
> >
> > I replied this.
>
> You haven't. You're implementing this without any regards for prior art and
> design work that's been done. You certainly can implement this internally
> however you want, but the end result has to match certain expectations, and
> designs. Your implementation won't, and as a result won't be discoverable.
>
>
I feel minor confusion here. (Hoping i am correct)
This feature is similar to what we are using presently to type U+
characters. Its global setting.
Example: Control+Shift+u  followed by unicode character code.
control+shift+u + 0915  gives me क
Please note, there is already ibus ime available for this.. ibus-rawcode
[1] which does this thing. You need to install this, i normally do this
when i need to type more unicode characters.

Same way:
For typing emoji, we are planning as follows:
Example: Control+shift+e followed by 'english word related to emoji'  [2]
It has bit more complexity compare to Unicode character. User need to type
whole word and single word gives you more options of emoji.
>From users perspective: If we want to type single Emoji, we can simply type
control+shift+e enter emoji and resume typing with current IME.
If user want to type many Emoji at a time. Then good to switch
(ibus-uniemoji) IME type all characters and switch back to previous IME.

So both control+shift+e and ibus-uniemoji has there own importance and
uses.

I am more inclined and use control+shift+e, since normally with one
sentence i use one emoji.

Hope it helps :)

Thanks,
Pravin Satpute


1. https://github.com/pravins/ibus-rawcode
2. http://unicode.org/emoji/charts/emoji-annotations.html#frown
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: F25 System Wide Change: Unicode 9.0 support

[pravin....@gmail.com]

missed this email :(

On 5 July 2016 at 23:19, Alexander Ploumistos 
wrote:

> Is there any point in updating fonts in rawhide to their Unicode 9.0
> versions, before the change is implemented?
>

With Unicode 9.0 update libraries will be updated with latest UCD stuff.


>
> Besides the font checking tools that do not know of Unicode 9.0 (or 8, I
> think), will anything important break after such an update?
>

There is no harm or even issues updating fonts prior to this change. Only
issue that might happen is, particular character not get required support
from harfbuzz and pango, since they do not know character properties and
how to render them.

Thanks,
Pravin Satpute
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

L10N String Breakage monitoring

[pravin....@gmail.com]

Hi all,

   Bringing this topic from meeting discussion to mailing list for
wider audience.

  Often after completion of translation package get updated with more
string or sometime translated .po file does not get pulled while
building package. This causes L10N string breakage.

   Anaconda is major candidate where we fail often with string breakage.

   We started this discussion in Fedora 23. Now we are thinking how we
could monitor this better. Following are some initial discussions
happened in G11N meeting. Just though to share with you all :)


Regards,
Pravin Satpute






05:17:28  #idea String Breakage monitoring (Jens, Akira)
05:18:01  juhp: tagoh_ any further idea on this.
05:18:14  I think we are tracking in i18n side.
05:19:20  We did not had any discussion last time, since juhp
and tagoh_ both were not available :)
05:19:25  I have been thinking about it a little...
05:19:37  not started to work on that but we know where
upstream repo is from zanata. it could be used to check by comparing
the POT in zanata and upstream?
05:20:08  nice idea.
05:20:24  How about discussing this as well in mailing list?
Even devel list is fine i think.
05:20:54  my current idea is to try track koji builds for some
specific packages looking for string changes
05:21:36  upstream is unstable.
05:21:55  part of it might be also tracking out of date POT/po files
05:21:59  umm, to me comparing .pot periodically or with
script looks more promising.
05:22:33  #idea String breakage monitoring - 1. Comparing POT
in Zanata and upstream.
05:22:43  how often do we check?
05:22:55  We do not
05:23:01  or plan to do the comparison?
05:23:16  assuming that they are properly branching and link
to zanata. if it doesn't work, they might use zanata  wrongly I
suppose.
05:23:57  aeng: that is idea proposed by tagoh_ and juhp  ,
to have some script or automation.
05:24:23  what is in zanata might not be in fedora though
05:24:29  yup
05:24:45  #idea String breakage monitoring - 1. Track Koji
builds for some specific packages looking for string changes.
05:24:48  juhp: right. so need to pick up projects we want to
keep on track
05:25:06  aeng, I would suggest daily or whenever there is a
build - depending on the approach we take
05:25:16  as we discussed Anacodda is major candidate here :)
05:25:31  tagoh_, ah no - I mean strings in zanata might not be
in fedora :)
05:25:44  additionally we might want to track projects not in Zanata
05:26:16  so the script might need to be dynamic enough
05:26:25  but leveraging zanata for this certainly also makes
some sense :)
05:26:52  or maybe we should look at both zanata, upstream and
package content
05:27:06  aeng, yeah
05:27:13  juhp: what is the original POT to compare then?
checking on the buildsys would need a cache to check right?
05:27:41  tagoh_, right so the script might have to
generate/cache POT files even
05:28:23  but if we really what to track fedora string breakage
then seems to me we need to look at what is actually in Fedora
05:29:51  also s/breakage/changes/
05:30:16  yeah, comparing with Fedora make sense
05:30:23  hm, that said those translations are coming from zanata :)
05:31:30  and detecting on the build time doesn't address
anything. we can just know "they broke it again".
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: [Test-Announce] 2015-03-19 Fedora 22 I18N Test Day

[pravin....@gmail.com]

On 19 March 2015 at 08:57, Akira TAGOH ta...@redhat.com wrote:

 Hi,

 We have a test day event for Internationalization on f22 as usual to make
 sure if f22 has any issues around i18n.
 Please join Freenode #fedora-test-day and try if your primary language
 works on f22 when you have a bit of time.
 Test cases and details are:

 https://fedoraproject.org/wiki/Test_Day:2015-03-19_i18n

 Also good to read:

 http://fedoramagazine.org/your-chance-to-contribute-in-fedora-22-development-cycle-through-test-days/

 All of feedbacks are valuable. even if you don't have a time today, you
 can try it anytime if you like.


We got nice badge from design team for same. :) [1]
Will award it next week to all testers provided feedback At results page.
[2]

Thanks,
Pravin Satpute

1. https://badges.fedoraproject.org/badge/i18n-test-day-participant
2. http://209.132.184.193/testdays/show_event?event_id=23
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Can you help with making fonts awesome in Fedora 21?

[pravin....@gmail.com]

On 16 October 2014 15:14, Richard Hughes hughsi...@gmail.com wrote:

 If you maintain a font in Fedora, or are a provenpackager, I could
 really need your help this weekend. Basically, we want to implement
 AppStream metadata[1] for all the fonts we want to show in the
 software center. I've already made a good start, and now other people
 are starting to help as well, so I'm pretty sure we can get the
 majority finished for next week when we can submit a mega-update of
 updated fonts.

 I've started a shared spreadsheet here:

 https://docs.google.com/spreadsheets/d/1o2sPWF7PEe6BKnBeZUI23m51nfFHUMx61IRsdNDozig/edit#gid=0
 with what needs doing -- if you can help, please put your FAS name in
 the second column and get building. If any fonts are missing that you
 think belong in the software center please feel free to add them.



Fedora i18n team was tracking this task. In todays meeting [1] we analyzed
status, more than 99% task completed and remaining are on the way.  Closed
the ticket [2].
Do comment/update if anything missing or further improvement needed.

Best Regards,
Pravin Satpute


1.https://fedoraproject.org/wiki/I18N/Meetings/2014-11-19
2. https://fedorahosted.org/i18n/ticket/38#comment:2
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Can you help with making fonts awesome in Fedora 21?

[pravin....@gmail.com]

On 16 October 2014 15:14, Richard Hughes hughsi...@gmail.com wrote:

 If you maintain a font in Fedora, or are a provenpackager, I could
 really need your help this weekend. Basically, we want to implement
 AppStream metadata[1] for all the fonts we want to show in the
 software center. I've already made a good start, and now other people
 are starting to help as well, so I'm pretty sure we can get the
 majority finished for next week when we can submit a mega-update of
 updated fonts.

 I've started a shared spreadsheet here:

 https://docs.google.com/spreadsheets/d/1o2sPWF7PEe6BKnBeZUI23m51nfFHUMx61IRsdNDozig/edit#gid=0
 with what needs doing -- if you can help, please put your FAS name in
 the second column and get building. If any fonts are missing that you
 think belong in the software center please feel free to add them.

 It's really easy to add content for fonts. This is an example with
 multiple subpackages:

 http://pkgs.fedoraproject.org/cgit/silkscreen-fonts.git/commit/?id=32acdd5aa900ad732c023a73f7cd269a136f0957
 and fonts with only one package are even easier, e.g.

 http://pkgs.fedoraproject.org/cgit/oflb-brett-fonts.git/commit/?id=72ff3099f733949f9526221b47a63eff9b9b969d


Thanks for templates :)

Will be very helpful if you can add how to test information as well. i.e.
after local install package will appear in gnome-software something in bit
detail.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: system-config-language-2.1.0 released

[pravin....@gmail.com]

cc'ing to devel list as well.


On 29 May 2014 11:26, pravin@gmail.com pravin@gmail.com wrote:

 Glad to see this happening after long time.


 On 29 May 2014 10:25, Parag Nemade pnem...@redhat.com wrote:

 Hi,
   It took some time but finally we have a working
 system-config-language[1] tool in Fedora rawhide. The major changes
 happened from 1.4.1 release to this 2.1.0 release are
 1) system-config-language GUI is re-written using PyGobject3 API's.
 2) system-config-language checks packages to install for any language
 using yum-langpacks instead of groups in comps file.


 Earlier s-c-l was using groupinstall which used to install fonts, IMES and
 l10n related packages. yum-langpacks only install l10n related package.

 If i remember correctly Bill mentioned earlier, intention behind langpack
 is to get rid of language related group and also mentioned
 https://bugzilla.redhat.com/show_bug.cgi?id=840885#c21 

 The groups are likely to be removed soon - input methods merged into the 
 input-methods group, and fonts into the font group.

 But question arise if layman users want to install IME and fonts packages
 related to his language, how he can accomplish that? With the present
 implementation either he need to install all fonts and IME's available in
 systems to get his desired language related package. This is definitely
 what we are looking for.

 I strongly feel langpacks should be compatible with groupinstall
 lang-support in long term.

 Regards,
 Pravin Satpute

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F21 Self Contained Change: Lohit Odia Gurumukhi font naming

[pravin....@gmail.com]

On 11 March 2014 19:25, Nicolas Mailhot nicolas.mail...@laposte.net wrote:


 Le Jeu 6 mars 2014 05:28, pravin@gmail.com a écrit :

  Valid point.
  I will fix this by adding fontconfig Aliases. We can keep it for couple
 of
  releases.

 It costs little to keep them forever now

 Documents have a very long lifetime


Fare enough. I done builds with suggested change.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F21 Self Contained Change: Lohit Odia Gurumukhi font naming

[pravin....@gmail.com]

Two changes done
1. Moved page with correct name for Gurmukhi script.
https://fedoraproject.org/wiki/Changes/Lohit_Odia_Gurmukhi
2. Propose this change as a System wide since might be there are some other
packages i am not aware using old names.

Let me know if anything still missing.

Best Regards,
Pravin Satpute





On 6 March 2014 10:00, pravin@gmail.com pravin@gmail.com wrote:




 On 6 March 2014 09:26, Kevin Kofler kevin.kof...@chello.at wrote:

 Jaroslav Reznik wrote:

  = Proposed Self Contained Change: Lohit Odia Gurumukhi font naming  =
  https://fedoraproject.org/wiki/Changes/Lohit_Odia_Gurumukhi
 
  Change owner(s): Pravin Satpute psatp...@redhat.com

 According to:

 http://snehakore.blogspot.com/2014/02/improvements-of-lohit-gurmukhi-2910.html
 the name should be Gurmukhi, not Gurumukhi.



 My bad.
 I will fix this, looks like i need to create different page with proper
 title.

 Regards,
 Pravin Satpute

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F21 Self Contained Change: Lohit Odia Gurumukhi font naming

[pravin....@gmail.com]

On 4 March 2014 19:12, Miloslav Trmač m...@volny.cz wrote:

 Hello,
 2014-03-03 15:31 GMT+01:00 Jaroslav Reznik jrez...@redhat.com:

 = Proposed Self Contained Change: Lohit Odia Gurumukhi font naming  =
 https://fedoraproject.org/wiki/Changes/Lohit_Odia_Gurumukhi

 snip

 This

 Other developers: N/A (not a System Wide Change)

 and this

 * Anaconda need to update default fonts installation list.
 * Libreoffice lang pack requires need to change.

 contradicts.

 Formally, the process calls for either making this a system-wide change,
 or for making the anaconda and libreoffice maintainers co-owners of the
 self-contained change.  (It amounts to the same thing - they need know
 about this.)


Yeah, I have completed most of the sections marked mandatory for system
wide change. I am fine with taking this as a system wide change.




 = User Experience =
 This change proposal it noticeable by target audience as the default font
 names for there language is going to change. They will see different font
 name.


 What about pre-existing documents that refer to the old font names?


I see this is the only place we have default fonts listed.
http://tagoh.fedorapeople.org/fonts/f20-defaultfonts.html
I think we can write clear i18n docs beat and mentioned about this change.



   Will they transparently use the new fonts?


Yes, since only font name is getting change. There will be not see much
difference in visual stuff.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F21 Self Contained Change: Lohit Odia Gurumukhi font naming

[pravin....@gmail.com]

On 5 March 2014 16:51, Miloslav Trmač m...@volny.cz wrote:

 2014-03-05 9:17 GMT+01:00 pravin@gmail.com pravin@gmail.com:

 On 4 March 2014 19:12, Miloslav Trmač m...@volny.cz wrote:

 Formally, the process calls for either making this a system-wide change,
 or for making the anaconda and libreoffice maintainers co-owners of the
 self-contained change.  (It amounts to the same thing - they need know
 about this.)


 Yeah, I have completed most of the sections marked mandatory for system
 wide change. I am fine with taking this as a system wide change.


 Getting an anaconda/libreoffice maintainer to sign up to make this
 self-contained might be easier - but that's purely up to you.


Sure, i will ping them.



  = User Experience =
 This change proposal it noticeable by target audience as the default
 font names for there language is going to change. They will see different
 font name.


 What about pre-existing documents that refer to the old font names?


 I see this is the only place we have default fonts listed.
 http://tagoh.fedorapeople.org/fonts/f20-defaultfonts.html
 I think we can write clear i18n docs beat and mentioned about this change.


 No, I meant users' documents.  If I have a used LibreOffice to create a
 document in F20, will it contain the old font names?  Will it automatically
 use the corresponding renamed fonts on F21, or will it fall back to some
 kind of default?


Valid point.
I will fix this by adding fontconfig Aliases. We can keep it for couple of
releases.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F21 Self Contained Change: Lohit Odia Gurumukhi font naming

[pravin....@gmail.com]

On 6 March 2014 09:26, Kevin Kofler kevin.kof...@chello.at wrote:

 Jaroslav Reznik wrote:

  = Proposed Self Contained Change: Lohit Odia Gurumukhi font naming  =
  https://fedoraproject.org/wiki/Changes/Lohit_Odia_Gurumukhi
 
  Change owner(s): Pravin Satpute psatp...@redhat.com

 According to:

 http://snehakore.blogspot.com/2014/02/improvements-of-lohit-gurmukhi-2910.html
 the name should be Gurmukhi, not Gurumukhi.



My bad.
I will fix this, looks like i need to create different page with proper
title.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Source string contextualization

[pravin....@gmail.com]

On 24 January 2014 17:52, Nilamdyuti Goswami ngosw...@redhat.com wrote:

 Hi all,

 While translating some of the fedora packages we often come across some
 source strings whose context or meaning is not clear. This results in wrong
 translations which is discovered later while using the actual application.
 This in turn effects the concerned application.

 To solve this issue, we have formed a Fedora SIG named Source String
 Contextualizing Group [1] aimed at
 providing concise yet meaningful description of the concerned source
 strings in the source code itself to ensure the correctness and quality in
 the resulting translations.

 We welcome feedback and suggestions.


I liked this.

I think this should become habit/protocol for translation community over a
period. Whenever one find any confusing string, they should report it back
to developer saying we need context Or they can give patch or suggestion
for same.

If every translator keeps on following it, in long term we will definitely
have term with good information.

Same time more information is not required for each and every word, only
for confusing terms. It make this task more achievable.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Calibri/Cambria replacements Carlito/Caladea

[pravin....@gmail.com]

On 10 October 2013 14:19, Caolán McNamara caol...@redhat.com wrote:

 I see that recently chromium appears to have commissioned two fonts
 claimed to be metrically equivalent to Calibri and Cambria. Which is
 super great from the perspective of giving LibreOffice a decent shot at
 laying out Microsoft Office documents that use the default Calibri
 equivalently.


Great news !!


 It would be really helpful if someone could package these
 up for Fedora.


I will take care of it.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fonts with default Fedora installation

[pravin....@gmail.com]

On 27 August 2013 14:04, Nicolas Mailhot nicolas.mail...@laposte.netwrote:


 Le Mar 27 août 2013 06:34, pravin@gmail.com a écrit :

  Yeah.
  If someone does specific request for SMP we should go ahead with it. At
  the
  end of days it is going to take only some kb's space in ISO's.

 I know it's probably wishful thinking on my part, but it would be great if
 all the local Fedora orgs (ambassadors…) spent a little time checking our
 default fonts are suitable for their locale and suggested alternatives if
 not. i18n shouldn't be centralized the way it is now. (we have good Greek
 coverage for example because in the past Greek people got involved and
 pointed us to the Greek Font Society, but unfortunately this is the
 exception not the rule)


Yes, i do agree.
Presently we have more options and can be bit more choosy for default font.
http://tagoh.fedorapeople.org/fonts/f19-defaultfonts.html  can be useful
for this.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fonts with default Fedora installation

[pravin....@gmail.com]

Added devel list proper email id.

Regards,
Pravin S


On 26 August 2013 17:15, pravin@gmail.com pravin@gmail.com wrote:

 Hi,

   Recently i done packaging of google-noto-fonts [1] for Fedora. With this
 font we got number of new script fonts of Unicode which were not available
 earlier. [2]

   Just done editing of comps file and my question is out of these script
 fonts how many we suppose to install by default.

   Presently we are following like at least one fonts for each script
 should be available with default installation, so if anyone while browsing
 web etc can get correct rendering for his script.

   But here issue is supporting whole Unicode with default installation
 will be too much.

   Might be we should only install fonts for BMP of Unicode and lets have
 other fonts installed by users when required (we do have feature in Fedora
 where if any fonts are not installed by default fontconfig search for
 particular script fonts.)

   I have done comps editing by keeping above thing in mind. If anyone have
 other suggestion please let me know.

 Best Regards,
 Pravin Satpute



 1. https://admin.fedoraproject.org/pkgdb/acls/name/google-noto-fonts
 2. http://koji.fedoraproject.org/koji/buildinfo?buildID=456970

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fonts with default Fedora installation

[pravin....@gmail.com]

On 27 August 2013 00:57, Bill Nottingham nott...@redhat.com wrote:

 pravin@gmail.com (pravin@gmail.com) said:
 Recently i done packaging of google-noto-fonts [1] for Fedora. With
 this
   font we got number of new script fonts of Unicode which were not
 available
   earlier. [2]
  
 Just done editing of comps file and my question is out of these
 script
   fonts how many we suppose to install by default.
  
 Presently we are following like at least one fonts for each script
   should be available with default installation, so if anyone while
 browsing
   web etc can get correct rendering for his script.
  
 But here issue is supporting whole Unicode with default installation
   will be too much.
  
 Might be we should only install fonts for BMP of Unicode and lets
 have
   other fonts installed by users when required (we do have feature in
 Fedora
   where if any fonts are not installed by default fontconfig search for
   particular script fonts.)
  
 I have done comps editing by keeping above thing in mind. If anyone
 have
   other suggestion please let me know.

 Sticking to the BMP is probably a good starting point, although I can see
 desktop installations wanting the emoji subset of the SMP installed out of
 the box.


Yeah.
If someone does specific request for SMP we should go ahead with it. At the
end of days it is going to take only some kb's space in ISO's.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Liberation 2.0 font development plan based on croscore fonts.

[pravin....@gmail.com]

On 21 May 2012 11:53, pravin@gmail.com pravin@gmail.com wrote:

 Hi All,

   Most of you aware regarding liberation license problem we are facing
 from long time. Looks like time came when we can get rid of it.

  Google has recently released google-croscore fonts.
 -  These are from same vendor ascendar with OFL license and more glyph
 coverage than existing liberation.
 -  Existing shape in liberation and same as croscore since from the
 same vendor.

   Plan:
 - Use base of croscore fonts and apply enhancements available in
 liberation and call new entity liberation 2.0

   Advantage:
1. Liberation license issues will get resolved
2. Liberation user community will get enhanced fonts. i.e. more
 language coverage.

   Need help from legal for doing licensing stuff, dunno how we can crack
 licensing of Liberation SansNarrow.



I have completed initial work. Yet not able to solve LiberationSansNarrow
licensing stuff might be it will take some more time. Updated .sfd's are
available in upstream master branch.
Planning to release it by Friday, early testing is welcome.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Liberation 2.0 font development plan based on croscore fonts.

[pravin....@gmail.com]

On 11 July 2012 18:55, Nicolas Mailhot nicolas.mail...@laposte.net wrote:


  On 07/11/2012 02:58 PM, Andrew Haley wrote:
  On 07/11/2012 08:51 AM, pravin@gmail.com wrote:
  I have completed initial work. Yet not able to solve
  LiberationSansNarrow
  licensing stuff might be it will take some more time
 
  Most people reading devel probably don't know what the
  LiberationSansNarrow
  licensing problem is.
 
  The problem is that particular variant was donated by Oracle under the
  Liberation license and Google croscore doesn't have that variant either.
   So we are basically struck with it for now.

 And Oracle did it because they wanted an Arial Narrow replacement for
 OpenOffice.org, so I doubt they'll participate in any relicensing now that
 they got rid of this product line (I'd be delighted to be proven wrong!)

 It sucks but that means for now the project should probably be split in
 two: Liberation v2 with OFL license gased on Google files, and v1 keeping
 only Narrows with the old Liberation License


Yes, that is the present plan.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Liberation 2.0 font development plan based on croscore fonts.

[pravin....@gmail.com]

Hi All,

  Most of you aware regarding liberation license problem we are facing from
long time. Looks like time came when we can get rid of it.

 Google has recently released google-croscore fonts.
-  These are from same vendor ascendar with OFL license and more glyph
coverage than existing liberation.
-  Existing shape in liberation and same as croscore since from the
same vendor.

  Plan:
- Use base of croscore fonts and apply enhancements available in
liberation and call new entity liberation 2.0

  Advantage:
   1. Liberation license issues will get resolved
   2. Liberation user community will get enhanced fonts. i.e. more language
coverage.

  Need help from legal for doing licensing stuff, dunno how we can crack
licensing of Liberation SansNarrow.

Regards,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Liberation 2.0 font development plan based on croscore fonts.

[pravin....@gmail.com]

On 21 May 2012 23:08, Nicolas Mailhot nicolas.mail...@laposte.net wrote:


 Le Lun 21 mai 2012 08:23, pravin@gmail.com a écrit :

  - Use base of croscore fonts and apply enhancements available in
  liberation and call new entity liberation 2.0

 That would be great !

 (but please don't add the 2.0 to the name)


Yes sure.

Thanks,
Pravin Satpute
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel