From kde-i18n-doc Sat Jun 13 05:03:20 2020 From: =?iso-8859-1?Q?=22I=F1igo_Salvador_Azurmendi=22?= Date: Sat, 13 Jun 2020 05:03:20 +0000 To: kde-i18n-doc Subject: Re: plasma 5.19.0 Message-Id: X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=159202464119695 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--Boundary_(ID_aKzDJEQc2P3vpkQmewZslg)" This is a multi-part message in MIME format. --Boundary_(ID_aKzDJEQc2P3vpkQmewZslg) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Content-disposition: inline =3E 2020ko ekainak 12an=2C ostirala=2C 18=3A26etan Jonathan Riddell-ek =3C= jr=40jriddell=2Eorg=3E idatzi zuen=3A =3E On Mon=2C 8 Jun 2020 at 14=3A42=2C =22I=F1igo Salvador Azurmendi=22 = =3Cxalba=40clientes=2Eeuskaltel=2Ees=3E wrote=3A =3E By the way=2C in around a weeks time an update to 5=2E19 will be rel= eased=2E Do you know when the announcement for 5=2E19=2E1 can be availab= le for translation=3F =3E I don=27t currently make the bugfix Plasma release announcements ava= ilable ahead of time i=27m afraid=2E=A0 This is because they are short s= pace fillers with the only part which is changed is the highlighted bugf= ixes=2C and those aren=27t written until the release day because often t= hey=27re not committed until release day=2E=A0 I can=27t really work out= a better way to organise this=2E https=3A//kde=2Eorg/announcements/plas= ma-5=2E18=2E1=2Ephp It is understandable=2C don=27t worry=2E =3E Jonathan =A0 --Boundary_(ID_aKzDJEQc2P3vpkQmewZslg) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Content-disposition: inline =26gt=3B 2020ko ekainak 12an=2C ostirala=2C 18=3A26etan Jonathan Riddell= -ek =26lt=3Bjr=40jriddell=2Eorg=26gt=3B idatzi zuen=3A=3Cbr=3E=3Cbr=3E=3C= div dir=3D=22ltr=22=3E=3Cdiv dir=3D=22ltr=22=3E=3Cfont style=3D=22font-s= tyle=3A normal=3B font-weight=3A normal=3B background-color=3A rgb(245=2C= 248=2C 240)=3B font-size=3A 14px=3B=22=3E=26gt=3B =3C/font=3EOn Mon=2C = 8 Jun 2020 at 14=3A42=2C =22I=F1igo Salvador Azurmendi=22 =26lt=3B=3Ca h= ref=3D=22javascript=3Amain=2Ecompose(=27new=27=2C=27t=3Dxalba=40clientes= =2Eeuskaltel=2Ees=27)=22=3Exalba=40clientes=2Eeuskaltel=2Ees=3C/a=3E=26g= t=3B wrote=3A=3Cbr=3E=3C/div=3E=3Cdiv class=3D=22gmail=5Fquote=22=3E=3Cb= lockquote class=3D=22gmail=5Fquote=22 style=3D=22margin=3A0px 0px 0px 0=2E= 8ex=3Bborder-left=3A1px solid rgb(204=2C204=2C204)=3Bpadding-left=3A1ex=22= =3E=3Cbr=3E=3Cdiv=3E=3Cfont style=3D=22font-style=3A normal=3B font-weig= ht=3A normal=3B background-color=3A rgb(245=2C 248=2C 240)=3B font-size=3A= 14px=3B=22=3E=26gt=3B =3C/font=3EBy the way=2C in around a weeks time a= n update to 5=2E19 will be released=2E Do you know when the announcement= for 5=2E19=2E1 can be available for translation=3F=3C/div=3E=3C/blockqu= ote=3E=3Cdiv=3E=3Cbr=3E=3C/div=3E=3Cdiv=3E=3Cfont style=3D=22font-style=3A= normal=3B font-weight=3A normal=3B background-color=3A rgb(245=2C 248=2C= 240)=3B font-size=3A 14px=3B=22=3E=26gt=3B =3C/font=3EI don=27t current= ly make the bugfix Plasma release announcements available ahead of time = i=27m afraid=2E=26nbsp=3B This is because they are short space fillers w= ith the only part which is changed is the highlighted bugfixes=2C and th= ose aren=27t written until the release day because often they=27re not c= ommitted until release day=2E=26nbsp=3B I can=27t really work out a bett= er way to organise this=2E =3Ca href=3D=22https=3A//kde=2Eorg/announceme= nts/plasma-5=2E18=2E1=2Ephp=22 target=3D=221=22=3Ehttps=3A//kde=2Eorg/an= nouncements/plasma-5=2E18=2E1=2Ephp=3C/a=3E=3C/div=3E=3Cdiv=3E=3Cbr=3E=3C= /div=3E=3Cdiv=3EIt is understandable=2C don=27t worry=2E=3Cbr=3E=3C/div=3E= =3Cdiv=3E=3Cbr=3E=3C/div=3E=3Cdiv=3E=3Cfont style=3D=22font-style=3A nor= mal=3B font-weight=3A normal=3B background-color=3A rgb(245=2C 248=2C 24= 0)=3B font-size=3A 14px=3B=22=3E=26gt=3B =3C/font=3EJonathan=3C/div=3E=3C= div=3E=3Cbr=3E=3C/div=3E=3Cdiv=3E=26nbsp=3B=3C/div=3E=3C/div=3E=3C/div=3E --Boundary_(ID_aKzDJEQc2P3vpkQmewZslg)--