H. İbrahim Güngör wrote:
> Merge please.
Done (branch and trunk).
Jürgen
On Wednesday 05 November 2008 15:14:51 Pavel Sanda wrote:
Hello,
I've updated the Turkish translation again. This time, all shortcut conflicts
are fixed. And some minor fixes too.
http://sudrap.org/repository/users/igungor/applications/lyx/tr.po
Merge please.
Kind Regards
PS: I had a pr
Hello,
I've updated the Turkish translation again. This time, all shortcut conflicts
are fixed. And some minor fixes too.
http://sudrap.org/repository/users/igungor/applications/lyx/tr.po
Merge please.
Kind Regards
ons to all..
Ugras
On Tue, Nov 11, 2008 at 12:41 PM, Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> On 11/11/2008 08:43, Ozgur Ugras BARAN wrote:
>
>> Hi Ibrahim,
>> I can help on Turkish translation, if you wish.. It's been a while I
>> didn't
>> part
On 11/11/2008 08:43, Ozgur Ugras BARAN wrote:
Hi Ibrahim,
I can help on Turkish translation, if you wish.. It's been a while I didn't
participate lyx..
You are very welcome to contribute again to the code too Ugras ;-)
Abdel.
On Tuesday 11 November 2008 09:43:20 Ozgur Ugras BARAN wrote:
> Hi Ibrahim,
> I can help on Turkish translation, if you wish.. It's been a while I didn't
> participate lyx..
Sure, i'll be glad if you can.
>
> Ugras
>
H. İbrahim Güngör
Hi Ibrahim,
I can help on Turkish translation, if you wish.. It's been a while I didn't
participate lyx..
Ugras
On Thu, Nov 6, 2008 at 1:07 AM, H. İbrahim Güngör <
[EMAIL PROTECTED]> wrote:
> On Thursday 06 November 2008 00:56:03 Pavel Sanda wrote:
> > H. ??brahim Güngö
H. ??brahim Güngör wrote:
> thanks for merge, please decide which way a newcomer translator must follow
> to
> update a po file. README.localizations *said* svn diff tr.po > tr.po.patch,
> but then it's changed to "just send whole updated file".
the later one is better.
pavel
On Thursday 06 November 2008 00:56:03 Pavel Sanda wrote:
> H. ??brahim Güngör wrote:
> > Many fixes and translations are also included.
> >
> > http://sudrap.org/repository/users/igungor/applications/lyx/tr.po
> >
> > Please merge.
>
> its in. next time please start work from the current version in
Pavel Sanda wrote:
>> Many fixes and translations are also included.
>>
>> http://sudrap.org/repository/users/igungor/applications/lyx/tr.po
>>
>> Please merge.
>
> its in.
Also in branch.
J??rgen
H. ??brahim Güngör wrote:
> Many fixes and translations are also included.
>
> http://sudrap.org/repository/users/igungor/applications/lyx/tr.po
>
> Please merge.
its in. next time please start work from the current version in svn tree.
pavel
On Wednesday 05 November 2008 20:03:33 =??B?SsO8cmdlbiBTcGl0em3DvGxsZXI=?=
wrote:
> Pavel Sanda wrote:
> >> Please update the Turkish translation file.
> >
> > its in.
>
> Since this file also made a huge improvement in branch, I've applied it to
> 1.5.
Pavel Sanda wrote:
>> Please update the Turkish translation file.
>
> its in.
Since this file also made a huge improvement in branch, I've applied it to
1.5.7svn.
J??rgen
H. ??brahim Güngör wrote:
> Please update the Turkish translation file.
its in.
pavel
ions/lyx/tr.po
>
> both tr.po & credits are now in.
> if you want complete tr.po to be part of 1.6.0 thursday morning seems to be
> the dealine :)
It's int *%96* state now, i think it's ready for the stable release :)
Updated translation file is still on:
http://sudrap.or
H. ??brahim Güngör wrote:
> Hello,
>
> I've just updated tr.po file. It's in %82 state for now and i'm going to
> improve it soon. Btw;
>
> I hereby grant permission for my contributions to LyX under the GNU General
> Public License (GPL) version 2 or later.
>
> PS: I couldn't attach the po f
Hello,
I've just updated tr.po file. It's in %82 state for now and i'm going to
improve it soon. Btw;
I hereby grant permission for my contributions to LyX under the GNU General
Public License (GPL) version 2 or later.
PS: I couldn't attach the po file due to the limitations. I'll keep the
u
>>>>> "Gürer" == Gürer Özen <[EMAIL PROTECTED]> writes:
>> Do you want me to take your translation in cvs for now? We do not
>> have a turkish translation distributed now, because it was out of
>> date. We normally have a policy of keeping only
> Merhaba!
Merhaba :)
> Changing the buffer code would imply a change from 8bit chars to
> 16/32bit chars. So this is a solution that will take a lot of time.
I see.
> OTOH producing utf-8 latex would be much simpler. Since it all goes
> through an ostream, one would only need a latin-9 to utf
> Do you want me to take your translation in cvs for now? We do not have
> a turkish translation distributed now, because it was out of date. We
> normally have a policy of keeping only language with half messages
> translated, but we can make an exception if you are committed to
>
Am Montag, 14. Februar 2005 15:58 schrieb Angus Leeming:
> I think you miss the point. He's talking about the display of the
> "Navigate" menu entries which are populated from the contents of the
> buffer. A "real" solution might be to have menu items that derive from
> QContentPane, but it see
using LyX/LaTeX for our documents and distribute it with
Gürer> our live CD. I've made a Turkish translation (mostly to qt
Gürer> frontend) available at http://6kere9.com/tr.po , it is based on
Gürer> the 1.3.5 release. I'll update it to the cvs version when i
Gürer> find free tim
Andreas Vox wrote:
>> > | I think there are two solutions for this problem. Best one is
>> > | modifying buffer code to accept and understand utf8. This will make
>> > | it possible to generate and use utf8 encoded files (something we aim
>> > | in our distribution).
>
> Merhaba!
>
> Changing the
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Lars Gullik BjÃnnes wrote:
>
> > GÃrer Ãzen <[EMAIL PROTECTED]> writes:
> >
> > | I think there are two solutions for this problem. Best one is modifying
> > | buffer code to accept and understand utf8. This will make it possible
> > | to generate a
Lars Gullik Bjønnes wrote:
> Gürer Özen <[EMAIL PROTECTED]> writes:
>
> | I think there are two solutions for this problem. Best one is modifying
> | buffer code to accept and understand utf8. This will make it possible
> | to generate and use utf8 encoded files (something we aim in our
> | distr
Gürer Özen <[EMAIL PROTECTED]> writes:
| I think there are two solutions for this problem. Best one is modifying
| buffer code to accept and understand utf8. This will make it possible to
| generate and use utf8 encoded files (something we aim in our
| distribution). Other one is doing charset con
Hi,
I'm a developer on Uludag Project (a national Linux distribution
targeted at Turkish users and government,
http://www.uludag.org.tr/en/ ).
We are using LyX/LaTeX for our documents and distribute it with our live
CD. I've made a Turkish translation (mostly to qt frontend) availab
27 matches
Mail list logo
