we (full) in projects: plugin - OpenGrok search results

Searched full:we (Results 1 – 25 of 4487) sorted by relevance

/plugin/elasticsearch/vendor/patrickschur/language-detection/resources/ug-Latn/
D	ug-Latn.txt	5 …zet-hörmitini shuningdek ularning barwer we tewrenmes hoquqini etrap qilishning dunyawi erkinlik, … 7 …we haqaret kelturush ewj élip kixilerning wijdanini bulghaydighan yawuz zorawanliqqa aylan'ghanliq… 9 insanlarning ilajisizliqtin zorawanliq we zulum ustide isyan köturimiz dep tewekkulige heriket qili… 13 …we qedir-qimmiti shuningdek er-ayallarning barawerlik hoquqi toghrisidiki eqidisini qayta tekitlig… 15 …ler teshkilati bilen hemkarliship, kishilik hoquqi we asasiy erkinlikning omumyuzluq hörmetlinishi… 17 ashu hoquq we erkinlikni omumyüzlük chushinishning shu qet'iy iradining toluq emelge ashurulushigha… 23 …we barliq dölet tiriship emelge ashuridighan ortaq ölchem süpitide mushu dunya kishilik hoquqi xit… 26 hemme adem zatidinla erkin, izzet-hörmet we hoquqta babbarawer bolup tughulghan. ular eqilghe we wi… 29 hemme adem mushu xitabnamide qeyt qilin'ghan barliq hoquq we erkinliktin behrimen bolush salahiyiti… 34 hemme adem hayatliqtin, erkinliktin we jismaniy bixeterliktin behrimen bolushqa hoquqluq. [all …]
/plugin/elasticsearch/vendor/patrickschur/language-detection/resources/bi/
D	bi.txt	7 …man i mekem se i gat ol nogud aksen i tekemples we oli mekem se pipol i kros, mo bambae wan taem i… 9 From se hemi wan impoten samting, sipos man i no fos blong lukaotem help, olsem wan las aksen we he… 13 …, oli disaed blong promotem sosol progres mo ol standed blong laef we i moa gud mo we i gat moa fr… 15 …ng ol raet blong man mo woman olbaot long wol mo gat ol stamba fridom taem we oli stap wok tugeta … 21 …we evri pipol mo evri kaontri long wol oli mas kasem, blong mekem se wanwan man mo woman insaed lo… 27 …we i stap long Deklereisen ia, wetaot eni kaen difrens, olsem long reis, kala blong skin, seks, la… 29 …el blong politik, eria we wok hem i kavremap o intenasonol level blong kaontri o teritori blong na… 38 …afa o mekem rabis fasin long hem, fasin we i nogud long man o woman o tritim man o woman long fasi… 41 Evriwan i gat raet blong narafala man i luksave hem olsem wan man o woman we i stap anda long loa. 44 …oa ia i protektem olgeta long ikwol fasin agensem diskrimineisen long taem we man mo woman i breke… [all …]
/plugin/bible/bible_douayRheims/
D	1_John.txt	1 …1:1. That which was from the beginning, which we have heard, which we have seen with our eyes, whi… 2 …1:2. For the life was manifested: and we have seen and do bear witness and declare unto you the li… 3 …1:3. That which we have seen and have heard, we declare unto you: that you also may have fellowshi… 4 1:4. And these things we write to you, that you may rejoice and your joy may be full. 5 …1:5. And this is the declaration which we have heard from him and declare unto you: That God is li… 6 1:6. If we say that we have fellowship with him and walk in darkness, we lie and do not the truth. 7 …1:7. But if we walk in the light, as he also is in the light, we have fellowship one with another:… 8 1:8. If we say that we have no sin, we deceive ourselves and the truth is not in us. 9 …1:9. If we confess our sins, he is faithful and just, to forgive us our sins and to cleanse us fro… 10 1:10. If we say that we have not sinned, we make him a liar: and his word is not in us. [all …]
D	1_Thessalonians.txt	2 …1:2. Grace be to you and peace. We give thanks to God always for you all: making a remembrance of … 5 … and in the Holy Ghost and in much fulness, as you know what manner of men we have been among you … 8 …so in every place: your faith which is towards God, is gone forth, so that we need not to speak an… 9 …1:9. For they themselves relate of us, what manner of entering in we had unto you: and how you tur… 12 …many things before and been shamefully treated, (as you know) at Philippi, we had confidence in ou… 14 …2:4. But as we were approved by God that the gospel should be committed to us: even so we speak, n… 15 …2:5. For neither have we used at any time the speech of flattery, as you know: nor taken an occasi… 16 2:6. Nor sought we glory of men, neither of you, nor of others. 17 …2:7. Whereas we might have been burdensome to you, as the apostles of Christ: but we became little… 18 …2:8. So desirous of you, we would gladly impart unto you not only the gospel of God but also our o… [all …]
D	2_Corinthians.txt	4 … in all our tribulation, that we also may be able to comfort them who are in all distress, by the … 6 …we be in tribulation, it is for your exhortation and salvation: or whether we be comforted, it is … 8 …we would not have you ignorant, brethren, of our tribulation which came to us in Asia: that we wer… 9 …1:9. But we had in ourselves the answer of death, that we should not trust in ourselves, but in Go… 10 …1:10. Who hath delivered and doth deliver us out of so great dangers: in whom we trust that he wil… 12 …t and sincerity of God, and not in carnal wisdom, but in the grace of God, we have conversed in th… 13 …1:13. For we write no other things to you than what you have read and known. And I hope that you s… 14 …1:14. As also you have known us in part, that we are your glory: as you also are ours, in the day … 23 …pare you, I came not any more to Corinth: not because we exercise dominion over your faith: but we… 34 2:11. That we be not overreached by Satan. For we are not ignorant of his devices. [all …]
D	2_Thessalonians.txt	3 …1:3. We are bound to give thanks always to God for you, brethren, as it is fitting, because your f… 4 …1:4. So that we ourselves also glory in you in the churches of God, for your patience and faith, a… 11 …1:11. Wherefore also we pray always for you: That our God would make you worthy of his vocation an… 13 …2:1. And we beseech you, brethren, by the coming of our Lord Jesus Christ and of our gathering tog… 24 …2:12. But we ought to give thanks to God always for you, brethren, beloved of God, for that God ha… 30 3:2. And that we may be delivered from importunate and evil men: for all men have not faith. 32 …3:4. And we have confidence concerning you in the Lord that the things which we command, you both … 34 …3:6. And we charge you, brethren, in the name of our Lord Jesus Christ, that you withdraw yourselv… 35 3:7. For yourselves know how you ought to imitate us. For we were not disorderly among you. 36 …3:8. Neither did we eat any man's bread for nothing: but in labour and in toil we worked night and… [all …]
D	Romans.txt	5 …1:5. By whom we have received grace and apostleship for obedience to the faith, in all nations, fo… 34 2:2. For we know that the judgment of God is, according to truth, against them that do such things. 66 …3:5. But if our injustice commend the justice of God, what shall we say? Is God unjust, who execut… 69 …3:8. And not rather (as we are slandered and as some affirm that we say) let us do evil that there… 70 …3:9. What then? Do we excel them? No, not so. For we have charged both Jews and Greeks, that they … 80 …3:19. Now we know that what things soever the law speaketh, it speaketh to them that are in the la… 89 3:28. For we account a man to be justified by faith, without the works of the law. 92 3:31. Do we then, destroy the law through faith? God forbid! But we establish the law. 93 4:1. What shall we say then that Abraham hath found, who is our father according to the flesh? 101 …doth it remain in the circumcision only or in the uncircumcision also? For we say that unto Abraha… [all …]
/plugin/findologicxmlexport/vendor/hoa/ustring/Documentation/En/
D	Index.xyl	16 <p>When we manipulate strings, the <a href="http://unicode.org/">Unicode</a> 26 Unicode. Unfortunately, sometimes we have to mix these extensions to achieve 43 interfaces. We are going to use three examples in three different languages: 48 <p>Now, let's see what we can do on these three strings.</p> 52 <p>Let's start with <strong>elementary</strong> operations. If we would like 53 to <strong>count</strong> the number of characters (not bytes), we will use 67 <p>When we speak about text position, it is not suitable to speak about the 70 We can know this direction thanks to the 95 <p>If we would like to <strong>concatenate</strong> another string to the end 96 or to the beginning, we will respectively use the [all …]
/plugin/webdav/vendor/sabre/dav/lib/CalDAV/
D	CalendarQueryValidator.php	35 // We'll parse it manually, as it's pretty simple. 51 * component we're checking should be specified, not the component to check 90 // If there are sub-filters, we need to find at least one component 97 // We had a match, so this comp-filter succeeds 103 // If we got here it means there were sub-comp-filters or 110 // If we got here it means we got through all comp-filters alive so the 120 * property we're checking should be specified, not the property to check 159 // If there are sub-filters, we need to find at least one property 167 // We had a match, so this prop-filter succeeds 173 // If we got here it means there were sub-param-filters or [all …]
/plugin/davcal/vendor/sabre/dav/lib/CalDAV/
H A D	CalendarQueryValidator.php	35 // We'll parse it manually, as it's pretty simple. 51 * component we're checking should be specified, not the component to check 92 // If there are sub-filters, we need to find at least one component 99 // We had a match, so this comp-filter succeeds 105 // If we got here it means there were sub-comp-filters or 112 // If we got here it means we got through all comp-filters alive so the 122 * property we're checking should be specified, not the property to check 163 // If there are sub-filters, we need to find at least one property 171 // We had a match, so this prop-filter succeeds 177 // If we got here it means there were sub-param-filters or [all …]
/plugin/asciidocjs/node_modules/pug-filters/node_modules/source-map/lib/
D	binary-search.js	21 * closest element that is smaller than or greater than the one we are 27 // 1. We find the exact element we are looking for. 29 // 2. We did not find the exact element, but we can return the index of 32 // 3. We did not find the exact element, and there is no next-closest 33 // element than the one we are searching for, so we return -1. 37 // Found the element we are looking for. 48 // we are in termination case (3) or (2) and return the appropriate thing. 62 // we are in termination case (3) or (2) and return the appropriate thing. 85 * closest element that is smaller than or greater than the one we are 100 // We have found either the exact element, or the next-closest element than [all …]
/plugin/asciidocjs/node_modules/source-map/lib/
D	binary-search.js	21 * closest element that is smaller than or greater than the one we are 27 // 1. We find the exact element we are looking for. 29 // 2. We did not find the exact element, but we can return the index of 32 // 3. We did not find the exact element, and there is no next-closest 33 // element than the one we are searching for, so we return -1. 37 // Found the element we are looking for. 48 // we are in termination case (3) or (2) and return the appropriate thing. 62 // we are in termination case (3) or (2) and return the appropriate thing. 85 * closest element that is smaller than or greater than the one we are 100 // We have found either the exact element, or the next-closest element than [all …]
/plugin/combo/vendor/antlr/antlr4-php-runtime/src/Atn/
H A D	ParserATNSimulator.php	44 * We begin with ATN simulation to build paths in a DFA. Subsequent prediction 50 * All of that is done without using the outer context because we want to create 51 * a DFA that is not dependent upon the rule invocation stack when we do a 52 * prediction. One DFA works in all contexts. We avoid using context not 57 * stacks in the configurations. When lack of context leads to a conflict, we 61 * When SLL yields a configuration set with conflict, we rewind the input and 64 * from the start rule. If we get a conflict using full context, then we can 65 * definitively say we have a true ambiguity for that input sequence. If we 70 * The next time we reach this DFA state with an SLL conflict, through DFA 71 * simulation, we will again retry the ATN simulation using full context mode. [all …]
H A D	PredictionMode.php	109 * As a heuristic, we stop prediction when we see any conflicting subset 110 * unless we see a state that only has one alternative associated with it. 118 * `12\|1\|[]` and `12\|2\|[]` conflict, but we cannot stop processing this 123 * After matching input A, we reach the stop state for rule A, state 1. 126 * However, alternative 3 will be able to continue and so we do not stop 127 * working on this state. In the previous example, we're concerned with 129 * associated with the conflicting configs, but since we can continue 134 * To handle pure SLL parsing, all we have to do is make sure that we 136 * predicate. From there, we can do the usual SLL termination heuristic. 148 * semantic predicate contexts so we might see two configurations like the [all …]
/plugin/webdav/vendor/sabre/dav/
D	CONTRIBUTING.md	11 We may not want to accept every feature that comes our way. Sometimes 14 We don't want to waste your time, so by having a quick chat with us first, 15 you may find out quickly if the feature makes sense to us, and we can give 18 If we don't accept the feature, it could be for a number of reasons. For 19 instance, we've rejected features in the past because we felt uncomfortable 26 In that case, definitely let us know about your plugin as well, so we can 29 We are often on [IRC][5], in the #sabredav channel on freenode. If there's 68 Any new feature or change requires unittests. We use [PHPUnit][7] for all our 73 we'd still _love_ your pull request. 75 We may have to write the tests ourselves, which can increase the time it takes [all …]
/plugin/davcal/vendor/sabre/dav/
H A D	CONTRIBUTING.md	11 We may not want to accept every feature that comes our way. Sometimes 14 We don't want to waste your time, so by having a quick chat with us first, 15 you may find out quickly if the feature makes sense to us, and we can give 18 If we don't accept the feature, it could be for a number of reasons. For 19 instance, we've rejected features in the past because we felt uncomfortable 26 In that case, definitely let us know about your plugin as well, so we can 29 We are often on [IRC][5], in the #sabredav channel on freenode. If there's 68 Any new feature or change requires unittests. We use [PHPUnit][7] for all our 73 we'd still _love_ your pull request. 75 We may have to write the tests ourselves, which can increase the time it takes [all …]
/plugin/doxycode/
D	action.php	45 … * updates the 'last_update' timestamp in the configuration, and then checks if we have an updated 50 …* for the cached snippets. We only want to invalidate the cached snippets if the configuration rea… 61 // we need this since we'll save the configuration later 62 // if we use the filtered configuration for saving we would remove all other elements 66 …// TODO: we could also use a filter function for filtering remote configurations with overdue upda… 84 … // on connection failures, we don't want to run the task runner constantly on failures! 86 … // if a new tag file is available we invalidate the cache if this tag file was used in a page! 90 $cachedHash = ''; // this is used to check if we really have a new file 92 // first read the old file and free memory so we do not exeed the limit! 109 // here we have the new content [all …]
/plugin/recaptcha2/lib/
D	autoload.php	`11 * then we can exit immediately. 16 /* All of the classes have names like "ReCaptcha\Foo", so we need 17 * to replace the backslashes with frontslashes if we want the 23 * we look here first, so that we don't waste time searching for 31 /* If we didn't find what we're looking for already, maybe it's`
/plugin/pureldap/vendor/freedsx/ldap/src/FreeDSx/Ldap/Server/ServerRunner/
H A D	PcntlServerRunner.php	35 * The time to wait, in seconds, before we run some clean-up tasks to then wait again. 40 * The max time to wait (in seconds) for any child processes before we force kill them. 65 * @var int[] These are the POSIX signals we handle for shutdown purposes. 101 // posix_kill needs this...we cannot clean up child processes without it on shutdown... 103 // We need to be able to handle signals as they come in, regardless of what is going on... 134 … * Check each child process we have and see if it is stopped. This will clean up zombie processes. 166 * children processes as we listen for new ones. 190 … // If there was no client received, we still want to clean up any children that have stopped. 211 // We are in the parent; the PID is the child process. 268 …* 1. Set a marker on the class signaling we are shutting down. This will reject incoming clien… [all …]
/plugin/minimap/_test/
D	minimap.test.php	54 $this->assertEquals(1, $count, "We should see the id"); 59 $this->assertEquals(1, $count,"We should see container for the whole map"); 64 $this->assertEquals(1, $count, "We should see one container for the header"); 69 $this->assertEquals(1, $count,"We should see one container for the pages"); 74 $this->assertEquals(2, $count, "We should see two pages"); 111 $this->assertEquals(1, $count, "We should see the id"); 116 $this->assertEquals(2, $count, "We should see two pages "); 121 $this->assertEquals(1, $count, "We should see the folder"); 153 $this->assertEquals(1, $count, "We should see the id"); 158 $this->assertEquals(1, $count, "We should see the folder"); [all …]
/plugin/cosmocode/lang/en/
D	support.txt	1 At CosmoCode, we offer a full range of professional DokuWiki services designed to meet your specifi… 2 custom plugin and template development to setup and ongoing support, we've got you covered. Our tea… 4 We additionally offer secure, reliable hosting solutions, and much more. 6 To learn more about how we can enhance your DokuWiki experience, visit our [[https://www.cosmocode.… 7 To contact us, please email us at <dokuwiki+support@cosmocode.de> and we will get back to you as so… 9 Please include the debug data below in your email, so we have a better understanding of your setup.
/plugin/webdav/vendor/sabre/vobject/lib/
D	TimeZoneUtil.php	29 // I'm not even kidding.. We handle this special case in the 118 * exception if we cannot accurately determine the timezone. 127 // First we will just see if the tzid is a support timezone identifier. 142 // That's why we're checking if we'll be able to successfully instantiate 143 // \DateTimeZone() before doing so. Otherwise we could simply instantiate 161 // Next, we check if the tzid is somewhere in our tzid map. 167 // and see if it is our tzid map. We don't want to check for this first just 176 // Maybe the author was hyper-lazy and just included an offset. We 177 // support it, but we aren't happy about it. 181 // already gets returned early in this function. Once we drop support [all …]
/plugin/nspages/printers/
D	printerTree.php	27 * We received the nodes all ordered together, but building the tree has probably 28 * lost the order for namespaces, we hence need to sort again each node 31 // We only need to sort "children". We don't need to sort "pages" because with the current 32 // workflow of the plugin nodes are provided already sorted to _print, and the way we 35 // That could save some CPU cycles because instead of sorting a big list we would sort 38 // have a custom sort (eg: "-h1") to ensure we don't have the correct order just because 93 // What we want is array ['a', 'b', 'c'] 122 // What we want is array ['a', 'b'] 134 * method is available only from PHP 8 so for now we re-implement this feature 141 if (empty($keys)){ // We've reach the end of the journey. We register the data of $item [all …]
/plugin/odt/ODT/
D	ODTState.php	29 * because they allow creation of a new paragraph. On leave() we throw the 30 * current state variables away and are safe back from where we came from. 31 * So we also don't need to worry about correct re-initialization of global 56 * If the function returns NULL then that means that we are 67 * If the function returns NULL then that means that we are 78 * If the function returns NULL then that means that we are 89 * If the function returns NULL then that means that we are 96 // us that we are in one. Otherwise we may find the paragraph 107 * If the function returns NULL then that means that we are 167 // We always will keep the initial state. [all …]
/plugin/icalevents/vendor/sabre/vobject/lib/
D	TimeZoneUtil.php	29 // I'm not even kidding.. We handle this special case in the 118 * exception if we cannot accurately determine the timezone. 127 // First we will just see if the tzid is a support timezone identifier. 143 // That's why we're checking if we'll be able to successfull instantiate 144 // \DateTimeZone() before doing so. Otherwise we could simply instantiate 163 // Next, we check if the tzid is somewhere in our tzid map. 169 // and see if it is our tzid map. We don't want to check for this first just 178 // Maybe the author was hyper-lazy and just included an offset. We 179 // support it, but we aren't happy about it. 184 // already gets returned early in this function. Once we drop support [all …]

12 3 4 5 6 7 8 9 10 >>...180

Project(s)

Full Search
Definition
Symbol
File Path
History
Type