omegat-l10n — Mailing list for OmegaT localizers.

[OmegaT-l10n] Request: macOS: Glossary Window acting as a OmegaT Window

[Martin E. <mar...@ic...>]

Hello,

At first, let me say that I truly enjoy using OmegaT. It fits perfectly my needs except for some small bugs and extensions I am now trying to get fixed:

In OmegaT I really love the Window-handling. If you are opening a Search-Window, it stays where it is, until you close it via ESC. Then the cursor is jumping back to the location you were working before. If you have several Search-Requests, you can just open several Windows, which stack, until you close them. 
If I want to cycle them on macOS I just use the command for that: “CMD + ~”, which is “CMD + ^” at the German keyboard layout – smooth move, not touching the mouse.

The problem:
If I would like to do the same with the Glossary-Window, which opens at “SHIFT + CMD + G”, it turns out that it’s not working. I cannot cycle back with that combination. But also, “CMD + TAB” is not working in here. The window seems unreachable via keyboard shortcuts, except the keystroke “SHIFT + CMD + G”, for which I have to lift my fingers from the keyboard to get back to the editor pane. 

I am very often hanging many hours in front of OmegaT, with a revised document, just to implement new words into the glossaries because my clients often have strict definitions I have to follow.

My Workflow-Workaround
My workflow now contains marking the untranslated word, hitting “SHIFT + CMD + G”, clicking back in the editor pane to move focus, and marking the translated word by hitting “SHIFT + CMD + G” again. With the Enter key, I am going to end the process of adding a word to the glossary. As far as that, it seems fine.

Solution
An approach could be to limit the Glossary-Window to only one, which does maybe make sense if there is some trouble in writing in the glossary file out of multiple Glossary-Windows, from what perspective I don’t have a clue. At this point, it is still appreciated to have that cycling key combo, which does the trick of switching back to the editor pane, which is normally onboard with macOS – but not functional in here. I think you missed to define the window as a new OmegaT-window somewhere, so that macOS cannot handle it as a new one. It just believes, that the complete arrangement out of the editor pane and Glossary-Window is all one big window.

For example, I took the word “bearing” and put it into the Glossary-Window as my source. In another step, I found out, that it does make more sense to add a second word like “bearing face”. So I would like to jump back to the editor pane again, where the word is still marked, hitting e.g. “SHIFT + OPTION + –>”, pressing  “SHIFT + CMD + G” again and voilà – added. If you do that in VIM mode, it’s even more understandable why you would like to avoid typing the extra word or moving the mouse.

To even go further, it would be unbelievably useful, if the cursor stayed where I left it in the Glossary-Window. For example, I left it at the Source-Term-Field and going back to the editor pane, changing my mind and selecting a different word. I would rather not have that as my Target-Term by default, which unfortunately is for now. I would like to decide to switch to the second part (e.g. via TAB key) by my own and then switch to the editor pane to pick the target. 
It’s absolutely fine to hit the “SHIFT + CMD + G” combo to place that into the right field at my Glossary-Window. 


Thank you very much for this convenient piece of software!

[OmegaT-l10n] How to Contribute to MyMemory directly using Set parameter from OmegaT

[Prasanta H. <pra...@gm...>]

Hi,
I'm using Mymemory MT to get suggestions for translations, but not able to
contribute my translated pairs to Mymemory directly. Instead I have to
create a TM and upload them to the website. I want to contribute right from
the OmegaT, Is there any separate plugins? They have an api for set methods
<https://mymemory.translated.net/doc/spec.php> but don't know how to use
them for OmegaT.

-- 
Thanks
with best regards
Prasanta Hembram

[OmegaT-l10n] Error in segment App_Glossaries.xml

[Valter M. <val...@ya...>]

Hi All
I found an error in the following segment, as per subject (double article):
The default writable glossary is located in *the* the <f0>glossary</f0> project folder and is called <f1>glossary.txt</f1>.
Ciao--
Valter
Free Software is better!

OmegaT: www.omegat.org

LibreOffice: www.libreoffice.org

KDE: www.kde.org

La bici non consuma e non produce emissioni, non ingombra e non fa rumore:

è un mezzo ecologico per definizione e ad alta efficienza energetica.

La bicicletta migliora il traffico, l'ambiente, la salute e l'umore.

[OmegaT-l10n] OmegaT Code Reading Sessions, part 4

[Jean-Christophe H. <jea...@tr...>]

Are you scared of being bored today ?

The “OmegaT Code Reading Sessions” offer an exciting opportunity to spend one hour of your life trying to make sense of OmegaT’s Java code…

Today is the 4th session. It will take place somewhere on a Jitsi instance, at 9pm Tokyo Time.

It’s nicer (but not required) if:
- you’re interested in OmegaT
- you’re not scared of reading code, even if that does not make any sense to your current self

You still want to join ?
- Take a look at this document:
    https://sr.ht/~brandelune/omegat-as-a-book/
- Take a look at what we’ve done so far:
    https://man.sr.ht/~brandelune/omegat-as-a-book/#omegat-as-a-book
- Subscribe to the (super low traffic) mailing list where I’ll post the link:
    https://lists.sr.ht/~brandelune/omegat-as-a-book

-- 
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/

[OmegaT-l10n] Help in the Spanish translation of OmegaT

[miriam g. r. <mir...@ho...>]

Hi!

I would like to volunteer to translate the latest version of OmegaT into Spanish. How do I get information about ongoing translation projects?

Regards,

Miriam.

[OmegaT-l10n] Fwd: Re: OmegaT 5.3 Release - Dutch (nl) updated

[Dick G. <th....@qu...>]

-------- Doorgestuurd bericht --------
Onderwerp: 	Re: OmegaT 5.3 Release - Dutch (nl) updated
Datum: 	Sat, 25 Jul 2020 14:20:40 +0200
Van: 	Dick Groskamp <th....@qu...>
Aan: 	Kos Ivantsov <ko...@om...>, OmegaT maillijst 
<ome...@li....>



Op 24-7-2020 om 22:09 schreef Kos Ivantsov:
> Dear OmegaT localisers,
> I hope this message finds you well.
> New OmegaT 5.3 release is going to be rolled out quite soon. If you 
> need to do anything in your projects which you want to be included in 
> the next release, please do it before July 31. I will also need a 
> message from you stating what needs to be included (by the same date).
> Thank you, and stay safe!
>
> --
> Kos

Kos,

Dutch project updated. (nl)

Changes are in:

Bundle properties
doc_src/Howto_SetupTeamProject.xml
doc_src/InstallingAndRunning.xml
doc_src/OmegaT4_EditorsPanes.xml
website/resources.html

so please include them in the new release

-- 
DiGro
___________________________
Apache OpenOffice 4.1.7 (Dutch) and scanned with Ziggo Safe Online (F-Secure)

Re: [OmegaT-l10n] OmegaT-L10n Digest, Vol 85, Issue 1

[Kos I. <ko...@om...>]

>
> Can someone delete danish translation https://github.com/OmegaT-L10N/da
> and remove me from the team to.
>
> I never manage to translate anything so nothing is translated.

Hi, you have been removed from the team a few months ago upon your 
previous request. The existence of a GitHub repository for Danish OmegaT 
localisation should not be of any concern of yours.

Have a great day,
--
Kos

[OmegaT-l10n] Delete OmegaT-L10N/da

[scootergrisen <sco...@gm...>]

Can someone delete danish translation https://github.com/OmegaT-L10N/da 
and remove me from the team to.

I never manage to translate anything so nothing is translated.

Re: [OmegaT-l10n] How to translate OmegaT

[Didier B. <d....@fr...>]

> -----Original Message-----
> From: scootergrisen [mailto:sco...@gm...]
> Sent: Wednesday, December 26, 2018 5:35 PM
> To: ome...@li...
> Subject: Re: [OmegaT-l10n] How to translate OmegaT
> 
> > There is one:
> > http://omegat.org/howtos/localizing_omegat
> 
> How do i update and already existing translation?

You contact Kos, the localisation manager.

He will create for you a team project, similarly to those:
https://github.com/OmegaT-L10N

Didier

Re: [OmegaT-l10n] How to translate OmegaT

[scootergrisen <sco...@gm...>]

> There is one:
> http://omegat.org/howtos/localizing_omegat

How do i update and already existing translation?

Re: [OmegaT-l10n] How to translate OmegaT

[Didier B. <d....@fr...>]

> -----Original Message-----
> From: scootergrisen [mailto:sco...@gm...]
> Sent: Wednesday, December 26, 2018 12:40 PM
> To: ome...@li...
> Subject: [OmegaT-l10n] How to translate OmegaT
> 
> I dont see any instructions on how to translate OmegaT just how to contribute
> in general.
> 
> I would like a page with instructions for translators.

There is one:
http://omegat.org/howtos/localizing_omegat


> Many other projects have a Contribute page with a Translate section that tells
> people what can be translated, how to submit translations etc.

Although it is a bit outdated, we have one.

If you contact the localisation manager, it can help you start.

Didier

Re: [OmegaT-l10n] index.html does not list all languages

[Didier B. <d....@fr...>]

> -----Original Message-----
> From: scootergrisen [mailto:sco...@gm...]
> Sent: Wednesday, December 26, 2018 12:42 PM
> To: ome...@li...
> Subject: [OmegaT-l10n] index.html does not list all languages
> 
> I see the file docs/index.html but the language list on that page does not match
> the languages in the folder.
> 
> Like there is a da/ folder but it does not say Danish (2.0.5) on the list.

Because there's no Danish documentation, only an instant start.

The index only lists full documentation.

> So many the index.html should be automatically generated or maybe just not
> used.

It is automatically generated.

Didier

[OmegaT-l10n] index.html does not list all languages

[scootergrisen <sco...@gm...>]

I see the file docs/index.html but the language list on that page does 
not match the languages in the folder.

Like there is a da/ folder but it does not say Danish (2.0.5) on the list.

So many the index.html should be automatically generated or maybe just 
not used.

[OmegaT-l10n] How to translate OmegaT

[scootergrisen <sco...@gm...>]

I dont see any instructions on how to translate OmegaT just how to 
contribute in general.

I would like a page with instructions for translators.
Many other projects have a Contribute page with a Translate section that 
tells people what can be translated, how to submit translations etc.

Re: [OmegaT-l10n] Localizing OmegaT 4.1.5 v2

[Marc R. I. <mar...@gm...>]

Hello fellow classmates,

It is great to have you interested in localising OmegaT. Coincidentally, I
happen to be part of the Catalan localization team too, and I have
contributed to a couple of strings since January this year. Let me give you
an overview of what has been done and what needs to be done for Catalan:

   - The user interface is half done, based on previous versions of OmegaT.
   In the localisation project, this is the Bundle.properties file, and it
   should be the first one to be translated, given that it is what the user
   sees first.
   - The documentation has not been started, although there was a Catalan
   translation for older versions of OmegaT. However, as the documentation
   refers to the user interface and describes it, it would make sense to
   translate it after the Bundle.properties file.

The Bundle.properties file alone has around 5,000 untranslated words, so
(fortunately for you) there is a lot of work you can do. Your contribution
will be highly appreciated, because it is a lot of work for only one person
and sometimes I simply do not have enough spare time to make the
translation advance.

Regarding the localisation workflow, the translation is carried out in
OmegaT itself using the Team Project feature, which connects OmegaT to
GitHub (where the source code is stored) and allows it to automatically
update the online files as you translate. All the formats you need to edit
are supported by OmegaT's filters and tags are easy to manage, so you will
not have problems with those.

As Didier said, Kos is the localisation manager and he will be able to
explain you everything with more details, and he will help you to set up
OmegaT and GitHub to start translating. I can also give you a hand at any
time either by email or in person regarding linguistic/style choices or
minor tech issues.

Regards,

*Marc Riera*


Missatge de Didier Briel <d....@fr...> del dia dg., 28 d’oct. 2018 a
les 14:37:

> Hello,
>
>
>
> I already replied to your previous message on 22/10 at 15:18. Did you
> receive it?
>
>
>
> What files for this version (4.1.5, 2) still need translation (into CA, ES
> or IT)?
>
>
>
> As I wrote in my reply, there is a current maintainer for the Italian
> OmegaT localisation, so nothing is required in Italian.
>
>
>
> To see exactly what is required to be translated to CA and ES, you can
> download the corresponding team projects:
>
> https://github.com/OmegaT-L10N/ca
>
> https://github.com/OmegaT-L10N/es
>
>
>
> Ask Kos (our localisation manager) for a user/password.
>
>
>
> Didier
>
>
>
> *From:* TPD Proyecto [mailto:loc...@ya...]
> *Sent:* Sunday, October 28, 2018 12:25 PM
> *To:* ome...@li...
> *Cc:* Tatiana Andrea Galli; Eugenia Maria; Maria Galofré Pujol;
> moi...@gm...
> *Subject:* Localizing OmegaT 4.1.5 v2
>
>
>
> Dear all,
>
>
>
> We are a group of master's students pursuing a degree in translation
> technologies at the Autonomous University of Barcelona.
>
>
>
>
>
> It is 4 of us. Our names are Tatiana (Taty), Eugenia, Moisés and Mariona.
> We have just joined the OmegaT localization plan and mailing list.
>
> For an assignment of one of our subjects, we would like to localize some
> materials of OmegaT (version 4.1.5, update 2). The languages we want to
> cover are Catalan, Spanish and Italian.
>
> We have just started learning about software localization and have some
> doubts regarding different aspects of our project.
>
> From what we have seen through the localization plan, pretty much all the
> tasks have been completed. We do know that the Catalan version of OmegaT's
> user interface needs to be completed, but we still have doubts of what
> other files we could contribute to translate.
>
> The localization plan shows what tasks are in progress at the moment but
> we are finding it a bit difficult to infer from that what files still need
> translation.
>
>
>
> We would be happy to collaborate translating any part of OmegaT (user
> manual, start guide, completing the user interface's translation into
> Catalan, etc.). However, our limitations are:
>
> -We have a deadline and a word count limit: more or less each of us should
> translate 2,000 words and the project has to be completely finished by mid
> December, including a presentation and a written paper that will also take
> some time.
>
> -We are not familiar with many file extensions. We can work with PO, XML,
> HTML, PROPERTIES and a few other basic formats.
>
> -We'd like to use OmegaT for the translation, although we can also work
> with other CAT tools. We don't know, however, how to apply filters with
> OmegaT that remove certain tags from the text, such as <b></b> for bold
> characters.
>
>
>
> To simplify a little, by now we would like to ask:
>
> What files for this version (4.1.5, 2) still need translation (into CA, ES
> or IT)?
>
>
>
>
>
> Thank you all in advance!
>
>
>
>
>
> Taty, Eugenia, Moisés, Mariona
>
>
>
>
>
>
> _______________________________________________
> OmegaT-L10n mailing list
> Ome...@li...
> https://lists.sourceforge.net/lists/listinfo/omegat-l10n
>

Re: [OmegaT-l10n] Localizing OmegaT 4.1.5 v2

[Didier B. <d....@fr...>]

Hello,

 

I already replied to your previous message on 22/10 at 15:18. Did you receive it?

 

What files for this version (4.1.5, 2) still need translation (into CA, ES or IT)?

 

As I wrote in my reply, there is a current maintainer for the Italian OmegaT localisation, so nothing is required in Italian.

 

To see exactly what is required to be translated to CA and ES, you can download the corresponding team projects:

https://github.com/OmegaT-L10N/ca

https://github.com/OmegaT-L10N/es

 

Ask Kos (our localisation manager) for a user/password.

 

Didier

 

From: TPD Proyecto [mailto:loc...@ya...] 
Sent: Sunday, October 28, 2018 12:25 PM
To: ome...@li...
Cc: Tatiana Andrea Galli; Eugenia Maria; Maria Galofré Pujol; moi...@gm...
Subject: Localizing OmegaT 4.1.5 v2

 

Dear all, 

 

We are a group of master's students pursuing a degree in translation technologies at the Autonomous University of Barcelona.

 

 

It is 4 of us. Our names are Tatiana (Taty), Eugenia, Moisés and Mariona. We have just joined the OmegaT localization plan and mailing list.

For an assignment of one of our subjects, we would like to localize some materials of OmegaT (version 4.1.5, update 2). The languages we want to cover are Catalan, Spanish and Italian.

We have just started learning about software localization and have some doubts regarding different aspects of our project.

>From what we have seen through the localization plan, pretty much all the tasks have been completed. We do know that the Catalan version of OmegaT's user interface needs to be completed, but we still have doubts of what other files we could contribute to translate.

The localization plan shows what tasks are in progress at the moment but we are finding it a bit difficult to infer from that what files still need translation.

 

We would be happy to collaborate translating any part of OmegaT (user manual, start guide, completing the user interface's translation into Catalan, etc.). However, our limitations are:

-We have a deadline and a word count limit: more or less each of us should translate 2,000 words and the project has to be completely finished by mid December, including a presentation and a written paper that will also take some time.

-We are not familiar with many file extensions. We can work with PO, XML, HTML, PROPERTIES and a few other basic formats.

-We'd like to use OmegaT for the translation, although we can also work with other CAT tools. We don't know, however, how to apply filters with OmegaT that remove certain tags from the text, such as <b></b> for bold characters.

 

To simplify a little, by now we would like to ask:

What files for this version (4.1.5, 2) still need translation (into CA, ES or IT)?

 

 

Thank you all in advance!

 

 

Taty, Eugenia, Moisés, Mariona

 

 

 

[OmegaT-l10n] Localizing OmegaT 4.1.5 v2

[TPD P. <loc...@ya...>]

Dear all, 
We are a group of master's students pursuing a degree in translation technologies at the Autonomous University of Barcelona.

It is 4 of us. Our names are Tatiana (Taty), Eugenia, Moisés and Mariona. We have just joined the OmegaT localization plan and mailing list.
For an assignment of one of our subjects, we would like to localize some materials of OmegaT (version 4.1.5, update 2). The languages we want to cover are Catalan, Spanish and Italian.
We have just started learning about software localization and have some doubts regarding different aspects of our project.
>From what we have seen through the localization plan, pretty much all the tasks have been completed. We do know that the Catalan version of OmegaT's user interface needs to be completed, but we still have doubts of what other files we could contribute to translate.The localization plan shows what tasks are in progress at the moment but we are finding it a bit difficult to infer from that what files still need translation.
We would be happy to collaborate translating any part of OmegaT (user manual, start guide, completing the user interface's translation into Catalan, etc.). However, our limitations are:-We have a deadline and a word count limit: more or less each of us should translate 2,000 words and the project has to be completely finished by mid December, including a presentation and a written paper that will also take some time.-We are not familiar with many file extensions. We can work with PO, XML, HTML, PROPERTIES and a few other basic formats.-We'd like to use OmegaT for the translation, although we can also work with other CAT tools. We don't know, however, how to apply filters with OmegaT that remove certain tags from the text, such as <b></b> for bold characters.
To simplify a little, by now we would like to ask:What files for this version (4.1.5, 2) still need translation (into CA, ES or IT)?

Thank you all in advance!

Taty, Eugenia, Moisés, Mariona

Re: [OmegaT-l10n] Registration for Microsoft Translator

[Didier B. <d....@fr...>]

From: mi...@mi... [mailto:mi...@mi...] 
Sent: Wednesday, September 05, 2018 4:59 PM
To: ome...@li...
Subject: [OmegaT-l10n] Registration for Microsoft Translator

 

I am translating http://omegat.org/howtos/ms_translator.html and other webpages from English to German. Does anybody know a link for registration for Microsoft Translator? The link provided in the documentation doesn’t work, several others via Azure also do not work, it seems, as if registration isn’t available anymore.

 

The registration still work, since I have one.

 

Try the following from Microsoft:

https://docs.microsoft.com/en-us/azure/cognitive-services/cognitive-services-apis-create-account

 

Didier

[OmegaT-l10n] Registration for Microsoft Translator

[<mi...@mi...>]

Hello,

 

I am translating http://omegat.org/howtos/ms_translator.html and other
webpages from English to German. Does anybody know a link for registration
for Microsoft Translator? The link provided in the documentation doesn't
work, several others via Azure also do not work, it seems, as if
registration isn't available anymore.

 

TIA

 

Michael

[OmegaT-l10n] Fail to save project properties with team project

[Johan v. B. <jo...@or...>]

Before reporting this as a bug, I thought I'd ask here.

I'm working on the Swedish localization in the shared repository on
github (OmegaT_L10N organization).

In OmegaT, I go to Project/Properties... and the Edit Project dialog
is displayed
I change the values for Glossary folder and Writable glossary files
(to existing directory/file)

When I close the dialog, OmegaT prompts to reopen the project. I click
OK and get the error message:

"Failed to load the specified project! java.lang.NullPointerException"

Is this a bug or are you not supposed to edit these proerties for team
projects? (in which case the error message could be improved)

/johan

Re: [OmegaT-l10n] Swedish Localization finally completed ...

[Johan v. B. <jo...@or...>]

Contact established, but thanks!

Den 4 dec. 2017 15:31 skrev "Didier Briel" <d....@fr...>:

> > -----Original Message-----
> > From: Johan von Boisman [mailto:jo...@or...]
> > Sent: Monday, December 04, 2017 1:53 PM
> > To: OmegaT l10n
> > Subject: [OmegaT-l10n] Swedish Localization finally completed ...
> >
> > ... just about an hour after the message about the new release went out.
> Darn
> > :-)
> >
> > I'm trying to find out where to send the files. As I understand, it's
> Kos Ivantsov
> > who's now the coordinator for that project and I tried to contact him
> through
> > the Sourceforge DM system.
>
> In case there's an issue with Sourceforge, you should try:
> ko...@om...
>
> Didier
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> OmegaT-L10n mailing list
> Ome...@li...
> https://lists.sourceforge.net/lists/listinfo/omegat-l10n
>

Re: [OmegaT-l10n] Swedish Localization finally completed ...

[Didier B. <d....@fr...>]

> -----Original Message-----
> From: Johan von Boisman [mailto:jo...@or...]
> Sent: Monday, December 04, 2017 1:53 PM
> To: OmegaT l10n
> Subject: [OmegaT-l10n] Swedish Localization finally completed ...
> 
> ... just about an hour after the message about the new release went out. Darn
> :-)
> 
> I'm trying to find out where to send the files. As I understand, it's Kos Ivantsov
> who's now the coordinator for that project and I tried to contact him through
> the Sourceforge DM system.

In case there's an issue with Sourceforge, you should try:
ko...@om...

Didier

[OmegaT-l10n] Swedish Localization finally completed ...

[Johan v. B. <jo...@or...>]

... just about an hour after the message about the new release went
out. Darn :-)

I'm trying to find out where to send the files. As I understand, it's
Kos Ivantsov who's now the coordinator for that project and I tried to
contact him through the Sourceforge DM system.

Should I do something else or just hang tight and wait for a reply?

"Hey Kos, maybe you're on this list! :-)"

Sincerely,
/jvb

Johan von Boisman
F:a Ordtrogen Översättning
Göteborg, SWEDEN
Telefon:   +46 709 46 65 26
Skype:    johan_v_b

Re: [OmegaT-l10n] Encoding issue in readme.utf8

[Didier B. <d....@fr...>]

> -----Original Message-----
> From: Johan von Boisman [mailto:jo...@or...]
> Sent: Sunday, November 05, 2017 9:35 AM
> To: Mailing list for OmegaT localizers.
> Subject: Re: [OmegaT-l10n] Encoding issue in readme.utf8
> 
> New discovery, different lf/cr scheme used:

That's "normal".

What we have done is that we have now forced readme.txt to be CRLF in distribution bundles, so that it will be readable with Windows Notepad.

For the other files, it doesn't really matter.

> I came across the afore mentioned encoding issue by chance when I
> downloaded the 4.1.2_02 package after having done localization work on the
> 4.1.2_01 package. Wanting to see what/if anything was different, I opened
> both in WinMerge to display a diff between the two, and the one in
> readme.utf8 was easy to spot since it was the only difference.
> 
> Now I had a look at src\org\omegat\Bundle.properties and noticed that you
> can't (easily) compare them as 4.1.2_01 uses Unix-style line endings ("\n")
> whereas 4.1.2_02 uses Windows style line endings
> ("\r\n")

If you really need to compare it with a tool that is bothered by different end of lines, change the end of lines in it with a text editor.

> I see this more like a nuisance than a real problem but it would be nice to solve
> it in the long term.
> 
> I'm slowly wrapping my head round Git and Github and noticed that when you
> push/pull to the github repo, Git will take care of any line ending conversions.

When you do a checkout from Subversion on Sourceforge, you get the same line ending conversion.

You can also do a checkout from Git on Sourceforge:
https://sourceforge.net/p/omegat/code/ci/master/tree/

> Is there any plan on moving to Github more definitely? 

Not currently.

>I'm aware of the
> "mirror" which is up already. I'm getting the feeling that Github is better suited
> to collaborative development than Sourceforge, but I may be wrong.

In that specific case, you are.

You are comparing files as stored in distribution bundles with files obtained through a checkout process.

As written above, unless explicitly forced to CRLF, text files in distribution bundles are LF only. That's how Gradle (the tool we use to make distribution bundles) works.

Didier

Re: [OmegaT-l10n] Encoding issue in readme.utf8

[Johan v. B. <jo...@or...>]

New discovery, different lf/cr scheme used:

I came across the afore mentioned encoding issue by chance when I
downloaded the 4.1.2_02 package after having done localization work on
the 4.1.2_01 package. Wanting to see what/if anything was different, I
opened both in WinMerge to display a diff between the two, and the one
in readme.utf8 was easy to spot since it was the only difference.

Now I had a look at src\org\omegat\Bundle.properties and noticed that
you can't (easily) compare them as 4.1.2_01 uses Unix-style line
endings ("\n") whereas 4.1.2_02 uses Windows style line endings
("\r\n")

I see this more like a nuisance than a real problem but it would be
nice to solve it in the long term.

I'm slowly wrapping my head round Git and Github and noticed that when
you push/pull to the github repo, Git will take care of any line
ending conversions.

Is there any plan on moving to Github more definitely? I'm aware of
the "mirror" which is up already. I'm getting the feeling that Github
is better suited to collaborative development than Sourceforge, but I
may be wrong.

PS. Just now I'm looking at the sourceforge repo and it looks like in
fact it is using Git for a VCS. You can fork and clone and checkout
and push and create pull requests into the main branch again like on
github? Maybe I should check that out.

/johan









Johan von Boisman
F:a Ordtrogen Översättning
Göteborg, SWEDEN
Telefon:   +46 709 46 65 26
Skype:    johan_v_b


2017-11-03 15:34 GMT+01:00 Didier Briel <d....@fr...>:
>> -----Original Message-----
>> From: Didier Briel [mailto:d....@fr...]
>> Sent: Friday, November 03, 2017 9:35 AM
>> To: 'Mailing list for OmegaT localizers.'
>> Subject: Re: [OmegaT-l10n] Encoding issue in readme.utf8
>>
>> > -----Original Message-----
>> > From: Johan von Boisman [mailto:jo...@or...]
>> > Sent: Friday, November 03, 2017 7:30 AM
>> > To: OmegaT l10n
>> > Subject: [OmegaT-l10n] Encoding issue in readme.utf8
>> >
>> > I just downloaded the OmegaT_4.1.2_02_Beta_L10N_Minimal.zip bundle and
>> > noticed that in
>> >
>> > OmegaT_4.1.2_02_Beta_L10N_Minimal\source\readme.utf8
>> >
>> > there's what looks like an encoding problem (screen dump is from
>> > Notepad++)
>> >
>> > In the 4.1.2_01_Beta[...] bundle, the same file has "[...] copyright©
>> > [insert year]. [...]"
>>
>> Thank you for the report.
>>
>> I confirm the issue.
>>
>> We'll check what happens.
>
> The issue was that Windows (the platform I use to build) didn't assume the file was in UTF-8.
>
> It was corrected, and future releases will have the correct text.
>
> Didier
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> OmegaT-L10n mailing list
> Ome...@li...
> https://lists.sourceforge.net/lists/listinfo/omegat-l10n