Mario Blättermann | 29 Jul 20:50 2014
Picon

Re: man-html translated in RO

Hi Mihai,

Am 29.07.2014 16:14, schrieb Mihai Cristescu:
> I would like to start also help2man after nano, but it seems the
> Romanian team is inactive. Last message on the list is from 2012, and
> Laurentiu's last message is that he has no longer time to make
> translations and ask for volunteers to continue the project.I sent
> another message today to the whole list, and wait for sign of life
> there. So, if there is nobody there who can revise the material, does
> it make sense to continue the translation?
> 
> Best regards,
> Mihai
> 
If really nobody responses within a reasonable time frame, or nobody of the
responders is willing to continue there as the new coordinator, then it would
become your job! First, write to the list, and if you don't get an answer next
two weeks, then the team and its list is to be considered as dead. Write then to
the global TP coordinators <coordinator <at> translationproject.org> (Benno
Schulenberg is one of them) to let the coordinatorship change.

Maybe you could ask some other Romanian translation teams for a review:

Gnome:
https://l10n.gnome.org/teams/ro/

KDE:
http://l10n.kde.org/team-infos.php?teamcode=ro

Launchpad:
(Continue reading)

Mario Blättermann | 27 Jul 22:05 2014
Picon

Re: man-html translated in RO

Hi Mihai,

Am 27.07.2014 13:43, schrieb Mihai Cristescu:
> Dear Mario,
> 
> Thanks for your reply and very good material you sent me.
> 
> Well, I was already finished translating the man files, after I have created a
> special filter based on regular expresions in memoq for importing groff files. 
> I was almost finished with the reviewing for errors. I also have generated the
> html files with groff-utf8 command.
> But, now after receiving your scripts I made some tests.
> Actually they work like a charm. I wish I had them before, they create much
> better quality of pot file (po4a seems a good tool for the future).
> 
> So, I have generated the ro.po file (combined from all text sources) and
> imported successfully in my CAT system, that means I can use the translation
> memory already done for this project.
> I have installed also Lokalize, Gtranslator and Poedit to have an idea and they
> all are good but I will keep working in memoq because I have more experience in
> it for complex tasks.
> Maybe for the future I'll start using Lokalize seems to have more features inside.
> 
> Question: After I finish translating the file, I send the material to this list
> or to the http://translationproject.org for revision?
> 
No, as Benno already wrote, you should contact the Romanian TP team for all
those issues.

> After I finish nano I can have a look also to help2man, but that is already
(Continue reading)

Benno Schulenberg | 27 Jul 20:50 2014
Picon

Re: man-html translated in RO


Hello Mihai,

On Sun, Jul 27, 2014, at 13:43, Mihai Cristescu wrote:
> Question: After I finish translating the file, I send the material to this
> list or to the http://translationproject.org for revision?

Anything in Romanian you will have to discuss with other
Romanian people, so on the mailing list of the Romanian
TP team, or other Romanian translator lists (Gnome, KDE,
Ubuntu...) if there is no response from the TP team.

> And is with this robot thing, for newr versions of the sources, how is that
> working?

That will show itself -- you will automatically receive a new
PO file (your previous PO file merged against the new POT)
via email whenever a new POT file is registered at the TP
for a domain that you translated.

Regards,

Benno

--

-- 
http://www.fastmail.fm - Email service worth paying for. Try it for free
Benno Schulenberg | 25 Jul 11:47 2014
Picon

Re: man-html translated in RO


Hi Mihai,

(For Mario: Mihai made Romanian translations of the nano docs, but
of the HTML pages.  I'm wondering, how are you getting along with
applying po4a to nano?)

On Fri, Jul 25, 2014, at 11:25, Mihai Cristescu wrote (quoted in full):
> Thanks for reply and sorry that the files can't be used in this form.
> I know that the html page are generated from the man groff format, but the
> thing is I am using a CAT system (memoQ) which uses a translation memory
> and speed up the translation process significantly.

Ah, very good.  Then, when the nano docs become available in
POT files, this translation memory will save you a lot of work.

> The problem is that I can't import the groff files into memoQ.
> 
> I have tried several approaches to convert the man groff files to: rtf ,
> ps, html formats which can be imported in memoQ, omegat , Trados SDL etc,
> but the issue is that there is no way to convert the translated files to
> man groff back. It seems that the only productive way to translate the man
> pages is to translate the files directly, but this is time consuming since
> you are not using a translation memory and term base.
> 
> Regarding po4a :
> I have installed yesterday this package on my arch system and followed the
> documentation. I succeeded converting the man pages to pot files, import
> them in memoQ, translated, but I was not able to convert back to man page
> (I had some strange errors on po4a-translate command) and I had to give up.
(Continue reading)

Benno Schulenberg | 25 Jul 11:01 2014
Picon

Re: man-html translated in RO


Hello Mihai,

On Thu, Jul 24, 2014, at 23:09, Mihai Cristescu wrote:
> I would like to send to the packager the man pages (html version)
> translated in Romanian language.

Nice.  However... it seems you have translated the HTML pages...
Those are generated files.  You should have translated the nano.1,
rnano.1 and rcnano.5 files instead.  :|  Of course the strings are
the same, just the formatting is different, but the HTML files are
generated from these files, not the other way around.

But... before you start moving all the strings over to the other
format, please wait.  A German translator, Mario Blättermann, is
working on a proposal to use po4a for the documentation of nano,
so if that happens, then all docs would be available as POT files too
-- much easier to handle.

Thanks for your work.  Meanwhile you may want to become a
member of the Romanian translation team at the TP and update
the Romanian interface translation of nano.
http://translationproject.org/team/ro.html
If you decide to do so, please write to the team leader, Laurentiu
Buzdugan, and if he does not respond, the to all of the team
members (in a single mail with many CCs).

Regards,

Benno
(Continue reading)

Mihai Cristescu | 24 Jul 23:09 2014
Picon

man-html translated in RO

Hello,

I would like to send to the packager the man pages (html version) translated in Romanian language.
Maybe you can include these files in the next release.
These files should be located in: /usr/share/nano/man-html/ro/
Thanks.
Best regards,
Mihai

Attachment (ro.zip): application/zip, 19 KiB
_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
The Kabal | 6 Jul 20:22 2014
Picon

Color highlighting feature request

Hello,

I noticed that for color highlighting, "Legal colors for foreground
and background color are: white, black, red, blue, green, yellow,
magenta, and cyan.".

I was attempting to create a close match to the "All Hallow's Eve"
color theme from Sublime Text 2, but noticed that I had very few
choices for colors in nano. By way of example, the 'comment' color
default for a PHP file in All Hallows Eve looks "purple". The closest
equivalent is the jarring magenta, which is really more of a bright
pink than a purple.

For environments with 256 color support, any chance we could get an
expanded selection of colors for syntax highlighting?

As always, your editor is awesome, many thanks for years of reliable
and easy to use editing.

- Patrick
Vampyrah Broadcasting | 13 Jun 21:29 2014
Picon

How to make all text bright?

Dear people,

How can I make all text bright?

Dennis
_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
Frank Schwenk | 12 Jun 09:18 2014
Picon

prevent nano from opening large files

Hi there,

i just made a huge mess as i had a large file open with "less" and by
pressing "v" accidentially i started the edit mode, which in this case
started nano.

Is it possible to prevent nano from opening large files? (.nanorc,
environment)

Regards

Frank
Mike Brown | 22 Mar 18:15 2014

command-line override of options set in .nanorc?

I usually want autoindent turned on, so my .nanorc has "set autoindent",
among many other customizations.

However, every once in a while, I need to copy-paste something that's 
preformatted, so it would be nice to be able to just override this one
setting when I invoke nano.

I was hoping there would be a command-line way to unset options that were set 
in the .nanorc. For example, for the single-letter options, you could use 
"-+" instead of "-", like in less(1):

  nano -+i

For the long option names, you would use an "unset" prefix:

  nano --unset-autoindent

There's no such capability, though, unless I'm missing something.
Is it possible? Maybe consider this a feature request.

(I realize I could remove the "set autoindent" from my .nanorc and instead
add -i or --autoindent to the command-line options, but it seems like the 
.nanorc is the ideal location for the things you want to be the defaults
most of the time, so I want to keep the autoindent set in there.)

Thanks for listening.
flyn jack | 12 Feb 05:32 2014
Picon

nanorc in Debian 7.3

OS Debian 7.3


I am confused. I know logic has its course, yet i need a definitive answer. The way that all instructions have a open end option to escape the legal weasel that is warm and fuzzy and could bite ones hand off, is frustrating at times.

Thank you.


man 1 nano or man 5 nanorc SYSCONFDIR/nanorc 


is described  


at a GNU page ' address below ' as “ files for configuring a host “ and “ This directory should normally be /usr/local/etc, but write it as $(prefix)/etc “.


So is it actually /etc  and not really  /usr/local/etc , while  /usr/local/ is empty in Debian 7.3


---------------------------

http://www.nano-editor.org/dist/v2.2/nano.1.html#INITIALIZATION FILE

INITIALIZATION FILE

nano will read initialization files in the following order: SYSCONFDIR/nanorc, then ~/.nanorc. Please see nanorc(5) and the example file nanorc.sample, both of which should be provided with nano.





--------------------------------------

http://www.gnu.org/prep/standards/html_node/Directory-Variables.html


‘sysconfdir’

The directory for installing read-only data files that pertain to a single machine–that is to say, files for configuring a host. Mailer and network configuration files, /etc/passwd, and so forth belong here. All the files in this directory should be ordinary ASCII text files. This directory should normally be /usr/local/etc, but write it as $(prefix)/etc. (If you are using Autoconf, write it as ‘ <at> sysconfdir <at> ’.)


_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano

Gmane