://builds.apache.org/job/Cocoon%202.1.X/104/])
COCOON-2350 Add a way to escape accolades in i18n messages (cdamioli:
[http://svn.apache.org/viewvc/?view=rev=1733754])
* BRANCH_2_1_X/src/java/org/apache/cocoon/xml/ParamSaxBuffer.java
> Add a way to escape accolades in i18n messa
[
https://issues.apache.org/jira/browse/COCOON-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cédric Damioli closed COCOON-2350.
--
Resolution: Fixed
I've implemented \{ as a way to escape { in i18n messages.
It's also
Cédric Damioli created COCOON-2350:
--
Summary: Add a way to escape accolades in i18n messages
Key: COCOON-2350
URL: https://issues.apache.org/jira/browse/COCOON-2350
Project: Cocoon
Issue
[
https://issues.apache.org/jira/browse/COCOON3-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed COCOON3-64.
-
Resolution: Fixed
i18n support
Key: COCOON3
/I18nTransformer.java
*
/cocoon/cocoon3/trunk/cocoon-sax/src/test/java/org/apache/cocoon/sax/component/I18NTransformerTest.java
* /cocoon/cocoon3/trunk/cocoon-sax/src/test/resources/i18n/fragment.xml
*
/cocoon/cocoon3/trunk/cocoon-sax/src/test/resources/i18n/fragment_en.properties
i18n support
[
https://issues.apache.org/jira/browse/COCOON3-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned COCOON3-64:
-
Assignee: Francesco Chicchiriccò
i18n support
[
https://issues.apache.org/jira/browse/COCOON3-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned COCOON3-64:
-
Assignee: (was: Francesco Chicchiriccò)
i18n support
[
https://issues.apache.org/jira/browse/COCOON3-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated COCOON3-64:
--
Fix Version/s: 3.0.0-beta-1
i18n support
/component/I18nTransformer.java
* /cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/xml
i18n support
Key: COCOON3-64
URL: https://issues.apache.org/jira/browse/COCOON3-64
Project: Cocoon 3
Issue
i18n support
Key: COCOON3-64
URL: https://issues.apache.org/jira/browse/COCOON3-64
Project: Cocoon 3
Issue Type: New Feature
Components: cocoon-pipeline, cocoon-sax, cocoon-servlet,
cocoon-sitemap
Affects
...
Gents,
I've just committed all the modifications involved with issue
COCOON3-64: I've ported the i18NTransformer in cocoon-sax (since no
additional dependencies are involved), added some unit tests and some
sitemap samples in cocoon-sitemap.
Nice I will try it out ASAP.
Thanks for
On 14/07/2011 09:25, Francesco Chicchiriccò wrote:
Hi folks,
yesterday Thorsten wrote something about C3 and i18n support, and we
also discussed something about this a while ago [1].
Since I need now this kind of support for my Hippo Cocoon Toolkit
project [2], I think in the next weeks I'll
/i18nTransformer.html
i18n support
Key: COCOON3-64
URL: https://issues.apache.org/jira/browse/COCOON3-64
Project: Cocoon 3
Issue Type: New Feature
Components: cocoon-pipeline, cocoon-sax, cocoon-servlet,
cocoon-sitemap
://builds.apache.org/job/Cocoon-trunk/51/])
COCOON3-64 #resolve
ilgrosso : http://svn.apache.org/viewvc/?view=revrev=1156644
Files :
* /cocoon/cocoon3/trunk/cocoon-sax/src/test/resources/i18n/base_it.properties
* /cocoon/cocoon3/trunk/cocoon-sax/src/test/resources/i18n/base_en.properties
*
/cocoon/cocoon3
Hi folks,
yesterday Thorsten wrote something about C3 and i18n support, and we
also discussed something about this a while ago [1].
Since I need now this kind of support for my Hippo Cocoon Toolkit
project [2], I think in the next weeks I'll be working on this topic,
so: is there anything I
On Wed, 2011-04-27 at 07:56 -0500, Peter Hunsberger wrote:
...
Actually it should not that be hard to port the i18n. IMO that is a MUST
HAVE featured and was very surprised to not find anything.
I'd agree, if we are going to use C3 in the future we will also need
this feature. I like
However I guess c3 only for is easiest for
everyone more familiar with c3. If we have a rewrite I can create the
c2.2 wrapper quite easy so I say do the c3 and when finish I do the
rest. ;)
Basically:
AbstractI18n = spring based transformer no deps to either c3/2.2
- c3I18n extends
Am 28.04.2011 16:12, schrieb Peter Hunsberger:
However I guess c3 only for is easiest for
everyone more familiar with c3. If we have a rewrite I can create the
c2.2 wrapper quite easy so I say do the c3 and when finish I do the
rest. ;)
Basically:
AbstractI18n = spring based transformer no
On 27/04/2011 07:26, Francesco Chicchiriccò wrote:
On 26/04/2011 19:04, Thorsten Scherler wrote:
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look hard enough or did we not have implemented in that
direction yet?
You're right, there seems to be nothing in C3
On Wed, 2011-04-27 at 09:45 +0200, Francesco Chicchiriccò wrote:
On 27/04/2011 07:26, Francesco Chicchiriccò wrote:
On 26/04/2011 19:04, Thorsten Scherler wrote:
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look hard enough or did we not have implemented
Am 27.04.2011 11:59, schrieb Thorsten Scherler:
On Wed, 2011-04-27 at 09:45 +0200, Francesco Chicchiriccò wrote:
On 27/04/2011 07:26, Francesco Chicchiriccò wrote:
On 26/04/2011 19:04, Thorsten Scherler wrote:
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look
to i18n/locale in c3.
Did I not look hard enough or did we not have implemented in that
direction yet?
You're right, there seems to be nothing in C3 sources related to i18n.
If so should we look into porting the old i18n transformer?
That sounds interesting: how much
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look hard enough or did we not have implemented in that
direction yet?
If so should we look into porting the old i18n transformer?
salu2
--
Thorsten Scherler thorsten.at.apache.org
codeBusters S.L. - web based systems
On 26/04/2011 19:04, Thorsten Scherler wrote:
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look hard enough or did we not have implemented in that
direction yet?
You're right, there seems to be nothing in C3 sources related to i18n.
If so should we look
of this issue because I believe there is no
ongoing work on this at the moment and it's not a blocker for 2.2 final release.
Improve i18n support
Key: COCOON-1675
URL: https://issues.apache.org/jira/browse/COCOON-1675
Project
[
https://issues.apache.org/jira/browse/COCOON-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht reassigned COCOON-2089:
Assignee: Felix Knecht
ServletService-FW handles missing i18n catalogue files incorrect
to get resource via servlet-services throws
CascadingIOException when Resource not found.
Adding CascadingIOException to catched exceptions and handle the same way like
a SourceNotFoundException.
ServletService-FW handles missing i18n catalogue files incorrect
handles missing i18n catalogue files incorrect
Key: COCOON-2089
URL: https://issues.apache.org/jira/browse/COCOON-2089
Project: Cocoon
Issue Type: Bug
Components
ServletService-FW handles missing i18n catalogue files incorrect
Key: COCOON-2089
URL: https://issues.apache.org/jira/browse/COCOON-2089
Project: Cocoon
Issue Type: Bug
I18n transformer doesn't substitute params within attribute values
--
Key: COCOON-2057
URL: https://issues.apache.org/jira/browse/COCOON-2057
Project: Cocoon
Issue Type: Bug
On 17 Nov 2006, at 13:54, Vadim Gritsenko wrote:
message key=upload.progress.sentSent: {0}% ({1} of {2}
bytes). Filename: {3}./message
I have not worked out yet how I18nTransformer does this
All the work is done in ParamSaxBuffer. So instead of using
On 16 Nov 2006, at 16:55, Vadim Gritsenko wrote:
Jeremy Quinn wrote:
Hi All
I am close to finishing an UploadProgressBar Dojo Widget for
CForms and am trying to implement i18n status messages.
I have a FlowScript that reads the upload status and sends this as
JSON to the UploadProgressBar
Jeremy Quinn wrote:
Now I need to work out how to do the above from FlowScript, when my i18n
messages may have parameters, eg :
:)
message key=upload.progress.sentSent: {0}% ({1} of {2} bytes).
Filename: {3}./message
I have not worked out yet how I18nTransformer does this
All
Hi Vadim
Many thanks for you reply :)
On 17 Nov 2006, at 13:54, Vadim Gritsenko wrote:
Jeremy Quinn wrote:
Now I need to work out how to do the above from FlowScript, when
my i18n messages may have parameters, eg :
:)
message key=upload.progress.sentSent: {0}% ({1} of {2}
bytes
Hi All
I am close to finishing an UploadProgressBar Dojo Widget for CForms
and am trying to implement i18n status messages.
I have a FlowScript that reads the upload status and sends this as
JSON to the UploadProgressBar.
I was trying to avoid using JXTemplate for the serialization
Jeremy Quinn wrote:
Hi All
I am close to finishing an UploadProgressBar Dojo Widget for CForms and
am trying to implement i18n status messages.
I have a FlowScript that reads the upload status and sends this as JSON
to the UploadProgressBar.
I was trying to avoid using JXTemplate
On 16 Nov 2006, at 16:55, Vadim Gritsenko wrote:
Jeremy Quinn wrote:
Hi All
I am close to finishing an UploadProgressBar Dojo Widget for
CForms and am trying to implement i18n status messages.
I have a FlowScript that reads the upload status and sends this as
JSON to the UploadProgressBar
this one now.
[i18n] extending the I18nTransformer
Key: COCOON-1379
URL: http://issues.apache.org/jira/browse/COCOON-1379
Project: Cocoon
Issue Type: Improvement
Components: * Cocoon Core
[
http://issues.apache.org/jira/browse/COCOON-1379?page=comments#action_12439250
]
Simone Gianni commented on COCOON-1379:
---
Has this ever been fixed? Because i recently committed a modification to i18n
transformer to made a couple
[ http://issues.apache.org/jira/browse/COCOON-1897?page=all ]
Jean-Baptiste Quenot closed COCOON-1897.
Resolution: Won't Fix
You probably need to validate user input before going through i18n. The only
thing that could be enhanced is to set
[
http://issues.apache.org/jira/browse/COCOON-1897?page=comments#action_12432078
]
Dennis Dam commented on COCOON-1897:
I'm wondering what the status is right now?
i18n transformer: catch date parsing exceptions silently
[ http://issues.apache.org/jira/browse/COCOON-1897?page=all ]
Antonio Gallardo updated COCOON-1897:
-
Would you provide a use case where is important to hide the exception?
i18n transformer: catch date parsing exceptions silently
, and makes your code less error
prone.
By the way, what we could also do is , instead of returning an empty string
(like in my patch), we return something more meaningful, like error or
invalid date format.
i18n transformer: catch date parsing exceptions silently
i18n transformer: catch date parsing exceptions silently
Key: COCOON-1897
URL: http://issues.apache.org/jira/browse/COCOON-1897
Project: Cocoon
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/COCOON-1897?page=all ]
DennisDam updated COCOON-1897:
--
Attachment: I18nTransformer.java.patch
i18n transformer: catch date parsing exceptions silently
[
http://issues.apache.org/jira/browse/COCOON-1897?page=comments#action_12429968
]
DennisDam commented on COCOON-1897:
---
patch applies to the current 2_1_X branch
i18n transformer: catch date parsing exceptions silently
Hi
We are using Cocoon 2.1(Web publishing Framework)
We have some problem in getting the i18n content in pages.
If we hardcode the key value like for instance,
i18n:textinput-text/i18n:text then the translated value is getting
printed (for example “output-text”),
For Example: input-text
sat2_waran said the following on 15/6/06 11:31:
Hi
We are using Cocoon 2.1(Web publishing Framework)
We have some problem in getting the i18n content in pages.
If we hardcode the key value like for instance,
i18n:textinput-text/i18n:text then the translated value is getting
printed
Hi
We are using Cocoon 2.1(Web publishing Framework)
We have some problem in getting the i18n content in pages.
If we hardcode the key value like for instance, i18n:texthome/i18n:text
then the translated value is getting printed, But if we give the key from
xsl variable,
i18n:textxsl:value
means that $home is not what you assume - I'd check the
output of this transform with the i18n transformer disabled, to see
what's being fed into it.
-Bertrand
-of select=$home//i18n:text it's not
coming...
Most probably means that $home is not what you assume - I'd check the
output of this transform with the i18n transformer disabled, to see
what's being fed into it.
Or it might means that the XSLT transformation is done *after* the
i18n
Peter Hunsberger wrote:
On 4/17/06, Adrien Guillon [EMAIL PROTECTED] wrote:
XSLT will be more extensible for site-specific configurations, and more
maintainable than the existing Java code.
I don't see that you'd necessarily have to mark the existing
implementation deprecated. Having the
I prefer XSLT... I believe it is much more maintainable if done properly...
especially with XSLT and XPath 2.0.
I wound up creating my own translation engine in XSLT 2.0, and it works quite
well. It only took a couple of hours, whereas the Java code was a mess to
trace through...
AJ
On 9
is always returned as zeros only.
Is this a known bug in i18n-transformer or java? Could someone please
verify this, so I can then report it to Jira.
Cocoon-2.1.9
Java 1.5.0 (beta 6)
Answering to my own question:
I added @src-locale=en_US to the i18n-tag, which helped. The transformer
was using the locale from my server, which caused incorrect formatting.
-Tuomo
On Tue, 23 May 2006, Tuomo L wrote:
Hello,
I'm trying to format currency using i18n:number. In the docs
[ http://issues.apache.org/jira/browse/COCOON-1587?page=all ]
Rolf Metternich closed COCOON-1587:
---
Resolution: Fixed
This was my special solution in earlier cocoon-versions.
Not longer useful!
[PATCH] Simple i18n support for selectionLists
Hello All,
The current implementation of the i18n transformer is able to output only a
single language in i18n:text tags. In the majority of cases this is what
is desired, however I need to be able to output multiple languages in a
single document. I'd like to extend the i18n text tag
On 17.04.2006 14:30, Adrien Guillon wrote:
2) Why use Java at all? Would we take that much of a performance hit if
we used straight XSLT? We could just aggregate the language packs and use a
stylesheet to process the i18n text nodes and substitute them. A large
dictionary would
I know I can write an i18n Transformer in XSLT faster than I can modify the
Java Code. Is this how we want to go?
I don't want to make something just for my applications, when I can contribute
the solution to the community. I feel we can make the change to an XSLT
implementation
Feel free to submit a patch. It would certainly be considered. It would
be helpful if you could also run some basic benchmarks to compare the
two implementations.
Ralph
Adrien Guillon wrote:
I know I can write an i18n Transformer in XSLT faster than I can modify the
Java Code. Is this how
On 4/17/06, Adrien Guillon [EMAIL PROTECTED] wrote:
I know I can write an i18n Transformer in XSLT faster than I can modify the
Java Code. Is this how we want to go?
I don't want to make something just for my applications, when I can contribute
the solution to the community. I feel we can
to
true.
The i18nSupport could be set by adding the attribute i18n-support=true to the
selection-list tag in the forms definition file.
( Example: fd:selection-list i18n-support=true
src=resources/selection-lists/tourart.xml/ )
In program code, you can add i18nSupport by using the SelectionList
Wrong i18n namespace constant in XMLResourceBundle
--
Key: COCOON-1700
URL: http://issues.apache.org/jira/browse/COCOON-1700
Project: Cocoon
Type: Bug
Components: * Cocoon Core
Versions: 2.1.8
Reporter
.
Wrong i18n namespace constant in XMLResourceBundle
--
Key: COCOON-1700
URL: http://issues.apache.org/jira/browse/COCOON-1700
Project: Cocoon
Type: Bug
Components: - Components: Sitemap
Versions: 2.1.8
the 2.0 one. This is also
reflected in I18nTransformer, but not in the XMLResourceBundle.
Wrong i18n namespace constant in XMLResourceBundle
--
Key: COCOON-1700
URL: http://issues.apache.org/jira/browse/COCOON-1700
,
Serviceable, Configurable, Disposable {
-/**
- * The namespace for i18n is http://apache.org/cocoon/i18n/2.1;.
- */
-public static final String I18N_NAMESPACE_URI =
-http://apache.org/cocoon/i18n/2.1;;
This breaks the compilation of 2.1.9-dev:
cocoon-block-forms-compile
On 30.11.2005 00:43, hepabolu wrote:
Author: joerg
Date: Tue Nov 29 13:00:03 2005
New Revision: 349807
URL: http://svn.apache.org/viewcvs?rev=349807view=rev
Log:
fixing bug COCOON-1700:
This breaks the compilation of 2.1.9-dev:
Please correct it.
Oh, sorry, I should have a look on the
Joerg Heinicke wrote:
On 30.11.2005 00:43, hepabolu wrote:
Author: joerg
Date: Tue Nov 29 13:00:03 2005
New Revision: 349807
URL: http://svn.apache.org/viewcvs?rev=349807view=rev
Log:
fixing bug COCOON-1700:
This breaks the compilation of 2.1.9-dev:
Please correct it.
Oh, sorry, I
[ http://issues.apache.org/jira/browse/COCOON-1670?page=all ]
Jörg Heinicke reassigned COCOON-1670:
-
Assign To: Cocoon Developers Team
portal tools i18n doesn't work
---
Key: COCOON-1670
URL: http
[ http://issues.apache.org/jira/browse/COCOON-1675?page=all ]
Jörg Heinicke reassigned COCOON-1675:
-
Assign To: Cocoon Developers Team
Improve i18n support
Key: COCOON-1675
URL: http://issues.apache.org
Hi,
Here is a patch which fixes the i18n in the forms samples. All it does
is add 2 lines to src/blocks/forms/samples/sitemap.xmap.
Judging by the sheer weight of this patch, I'm supposing that a jira
issue is not necessary.
--
Paul Fockehttp://outerthought.org
Paul Focke wrote:
Hi,
Here is a patch which fixes the i18n in the forms samples. All it does
is add 2 lines to src/blocks/forms/samples/sitemap.xmap.
Judging by the sheer weight of this patch, I'm supposing that a jira
issue is not necessary
Upayavira wrote:
Paul Focke wrote:
Hi,
Here is a patch which fixes the i18n in the forms samples. All it does
is add 2 lines to src/blocks/forms/samples/sitemap.xmap.
Judging by the sheer weight of this patch, I'm supposing that a jira
issue is not necessary
Paul Focke wrote:
Hi,
Here is a patch which fixes the i18n in the forms samples. All it does
is add 2 lines to src/blocks/forms/samples/sitemap.xmap.
Judging by the sheer weight of this patch, I'm supposing that a jira
issue is not necessary.
Applied. Thanks!
Sylvain
--
Sylvain Wallez
Improve i18n support
Key: COCOON-1675
URL: http://issues.apache.org/jira/browse/COCOON-1675
Project: Cocoon
Type: Task
Components: Blocks: Portal
Versions: 2.2-dev (Current SVN)
Reporter: Carsten Ziegeler
Fix For: 2.2-dev
Hi Roy,
Le 28 oct. 05, à 10:02, roy huang a écrit :
... I have update form the svn,only
src\webapp\samples\i18n\translations\messages_zh_CN.xml is
update,src\blocks\forms\java\org\apache\cocoon\forms\system\i18n\messag
es_zh_CN.xml is not updated.I think this file should be update too
Le 28 oct. 05, à 05:49, roy huang a écrit :
...messages_zh_CN.xml
Committed to both 21branch and trunk - I cannot check the translation
though, we trust you on that one!
-Bertrand
Hi,Bertrand
I have update form the svn,only
src\webapp\samples\i18n\translations\messages_zh_CN.xml is
update,src\blocks\forms\java\org\apache\cocoon\forms\system\i18n\messages_zh_CN.xml
is not updated.I think this file should be update too.
Thanks.
Roy Huang
On 28 Oct 2005, at 08:15, Bertrand Delacretaz wrote:
Le 28 oct. 05, à 05:49, roy huang a écrit :
...messages_zh_CN.xml
I cannot check the translation though, we trust you on that one!
That's when you use http://translate.google.com/translate_t (or a
wife who can read chinese)...
I
level - exactly what you would expect if you are trying to
debug i18n component. Anything else is counter productive
and counter intuitive (what you would do if you need to see
those exeptions? Set a breakpoint? Patch implementation?
Roll your own implementation?)
- Bad formed XML
that the system works.
Such exceptions must not bubble up upstream: if exception is let
through, your whole site goes down simply due to single bug in i18n
catalogue. With existing exception handling, i18n (and your whole
site) continues functioning with older version of the catalogue, but
reports an error
impression that the system works.
Such exceptions must not bubble up upstream: if exception is let
through, your whole site goes down simply due to single bug in i18n
catalogue. With existing exception handling, i18n (and your whole
site) continues functioning with older version of the catalogue
Vadim Gritsenko wrote:
Well I can see that in dev environment you would prefer to get error
right away, but historically i18n was allowing content editors to push
broken XML files and site admins to scream on editors, while all other
users can continue to use older version of a site.
Ah, I
Cocoon 2.1.5 and 2.2.0-dev. If i18n:text tags
are included in the initial file of a pipeline, the i18n transformer works
great. But if they are added via an XSL transformation, the i18n transfomer no
longer works. In this case, when the i18n:text tags are added via an XSL
transform, the logs
[ http://issues.apache.org/jira/browse/COCOON-1450?page=all ]
Ralph Goers updated COCOON-1450:
Bugzilla Id: (was: 33637)
Component: * Cocoon Core
(was: Blocks: (Undefined))
Description:
I've tried using i18n tags
level - exactly what you would expect if you are trying to
debug i18n component. Anything else is counter productive
and counter intuitive (what you would do if you need to see
those exeptions? Set a breakpoint? Patch implementation?
Roll your own implementation?)
- Bad formed XML
level - exactly what you would expect if you are trying to
debug i18n component. Anything else is counter productive
and counter intuitive (what you would do if you need to see
those exeptions? Set a breakpoint? Patch implementation?
Roll your own implementation?)
- Bad formed
: vgritsenko
Date: Tue Oct 11 15:28:46 2005
New Revision: 312968
URL: http://svn.apache.org/viewcvs?rev=312968view=rev
Log:
action dev=VG type=update
I18n: Refactored XMLResourceBundle to use transient store instead of
private cache. Added reload check interval parameter. Support
Ugo Cei wrote:
Il giorno 12/ott/05, alle ore 16:48, Vadim Gritsenko ha scritto:
Check your ~/.subversion/config, it should have [auto-props] section
set up. For files already added to the svn, use this shell script:
Would you be so nice as to share with us the contents of your [auto-
/show_bug.cgi?id=37079
Summary: I18N Transformer
Product: Cocoon 2
Version: 2.1.6
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: sitemap components
AssignedTo: dev
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37079.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Vadim Gritsenko wrote:
Ugo Cei wrote:
Would you be so nice as to share with us the contents of your [auto-
props] section? I assume you have added all filename patterns that are
relevant for Cocoon sources.
Done. Feel free to update.
http://wiki.apache.org/cocoon/SVNConfig
Surely
David Crossley wrote:
Vadim Gritsenko wrote:
Ugo Cei wrote:
Would you be so nice as to share with us the contents of your [auto-
props] section? I assume you have added all filename patterns that are
relevant for Cocoon sources.
Done. Feel free to update.
[EMAIL PROTECTED] wrote:
Added:
cocoon/blocks/core-samples-additional/trunk/samples/resources/i18n/messages.xml
URL:
http://svn.apache.org/viewcvs/cocoon/blocks/core-samples-additional/trunk/samples/resources/i18n/messages.xml?rev=314929view=auto
hepabolu wrote:
Grr. I checked this and thought it was properly set up. What should I
have done?
Check your ~/.subversion/config, it should have [auto-props] section set up. For
files already added to the svn, use this shell script:
#!/bin/sh
svn propset svn:eol-style native $*
svn
Vadim Gritsenko wrote:
hepabolu wrote:
Grr. I checked this and thought it was properly set up. What should I
have done?
Check your ~/.subversion/config, it should have [auto-props] section set
up. For files already added to the svn, use this shell script:
#!/bin/sh
svn propset
hepabolu wrote:
And Windows? At work I use Windows and handle all SVN actions using
subclipse.
Subclipse? You are asking wrong dude :-)
In TortoiseSVN probably there is some settings dialogue for that; and you can
use File - Properties - Subversion tab to edit properties.
Vadim
Il giorno 12/ott/05, alle ore 16:48, Vadim Gritsenko ha scritto:
Check your ~/.subversion/config, it should have [auto-props]
section set up. For files already added to the svn, use this shell
script:
Would you be so nice as to share with us the contents of your [auto-
props] section? I
...shouldn't this only be changed in trunk instead of in branch?
cheers
--
Torsten
PGP.sig
Description: This is a digitally signed message part
Torsten Curdt wrote:
...shouldn't this only be changed in trunk instead of in branch?
IMHO, if OOMEs and severe usability issues are not fixed in branch, then trunk
won't ever be used by anybody, isn't it?
Vadim
1 - 100 of 247 matches
Mail list logo
