Hi all,
I've been developing a small bash script to help me with some git tasks,
such as updating all my downloaded git clones, deleting all branches and,
the most important, commiting automatically PO files from the GUI (not
documentation).
Well, at this momment, I'm working with the PO filename
Hello,
I complained about this some time ago, but I can not find the thread. :)
I too wrote myself a basic script to do exactly what you described, but
shortly I found that was not enough. I had to change if frequently until I
ended up with the script that worked for UI translations that keep
tra
2011/12/10 Daniel Mustieles García :
> Hi all,
>
> I've been developing a small bash script to help me with some git tasks,
> such as updating all my downloaded git clones, deleting all branches and,
> the most important, commiting automatically PO files from the GUI (not
> documentation).
>
> Well
I agree with Matei: the bes solution would be if GUI files were always in
PO filder, and documentation files were in HELP folder, but there are some
incoveniences for it.
First of all, there isn't a written rule saying where PO files mus be. Each
developer chooses their location, and especifies it
Well,
looking at other projects there are at least three logical solutions that
some project use and do not complicate the system.
- first is creating different po-folders for extra translations, like /po,
/po-lalala, /po-help with xx.po files
- second is keeping the current path of /po, but renam
On Mon, Dec 12, 2011 at 08:39, Matej Urban wrote:
> Well,
>
> looking at other projects there are at least three logical solutions that
> some project use and do not complicate the system.
> - first is creating different po-folders for extra translations, like /po,
> /po-lalala, /po-help with xx.p
2011/12/12 Matej Urban
> Well,
>
> looking at other projects there are at least three logical solutions that
> some project use and do not complicate the system.
> - first is creating different po-folders for extra translations, like /po,
> /po-lalala, /po-help with xx.po files
> - second is keep
Op So, 2011-12-11 om 10:57 +0100 skryf Daniel Mustieles García:
> I agree with Matei: the bes solution would be if GUI files were always
> in PO filder, and documentation files were in HELP folder, but there
> are some incoveniences for it.
>
> First of all, there isn't a written rule saying wher
Headers can be split in two (or more) lines? I this case, how could a bash
script get the full path?
Thanks for your comment :)
2011/12/13 F Wolff
>
> Op So, 2011-12-11 om 10:57 +0100 skryf Daniel Mustieles García:
> > I agree with Matei: the bes solution would be if GUI files were always
> > i
What about this issue?
Is there any possibility to add headers to PO files? It could be possible,
at least, to add this header just to es.po files? It woulb be very useful
for me and for other translators/coordinators, and it is completely
transparent for translations (just note the X-Generator he
2011/12/29 Daniel Mustieles García
> What about this issue?
>
> Is there any possibility to add headers to PO files? It could be possible,
> at least, to add this header just to es.po files? It woulb be very useful
> for me and for other translators/coordinators, and it is completely
> transparen
Den 10-12-2011 20:37, Daniel Mustieles García skrev:
Hi all,
I've been developing a small bash script to help me with some git tasks,
such as updating all my downloaded git clones, deleting all branches
and, the most important, commiting automatically PO files from the GUI
(not documentation).
>> [: Daniel Mustieles García :]
>> I've been talking with with Claude about the possibility to add a header
>> (maybe «X-Location»?) to PO files (both GUI and doc ones) containing the
>> folder in which the PO file is located [...]
>
> [: Kenneth Nielsen :]
> [...]
> On another subject remember th
Hi Simos,
PO editors should be able to manage headers without eating them, and
translators doesn't use to edit PO files manually, btw, if this feature is
finally implemented in DL, it should be able to detect and fix malformed
headers.
Using an online XML file is another posibility, but I don't l
2012/1/2 Daniel Mustieles García
> Hi Simos,
>
> PO editors should be able to manage headers without eating them, and
> translators doesn't use to edit PO files manually, btw, if this feature is
> finally implemented in DL, it should be able to detect and fix malformed
> headers.
>
> Using an onl
Thanks for the idea, but using a "find" command may be easier :)
Btw, GUI files are always (unless some exceptions) in modulename/po, so I
just need use find to know where is the doc folder.
2012/1/3 Simos Xenitellis
>
> 2012/1/2 Daniel Mustieles García
>
>> Hi Simos,
>>
>> PO editors should
16 matches
Mail list logo